The host says it’s going to be messing with the network again tomorrow night:
On Thursday January 16th, in a 4 hour window starting at 10pm, we will be moving on to the next step of the Network Improvement Series maintenances. This step is going to involve migrating the network layer from the old hardware to the new designed setup. This is expected to be a near impact-free maintenance; all services will continue to work throughout the migration. As with all maintenances, we will proceed slowly to ensure that, should any problems occur, we will be able to address them quickly.
I mean, this doesn’t guarantee failure or anything, but I’ve seen enough network improvements to know what’s coming.
I’d almost forgotten this little place was here.
Might as well post something, just to keep the WP Overlords happy.
It says on the admin screen here that we’re allowed 3,072 MB for our individual spaces here at WordPress.com, which is a pretty fair amount of space when you get right down to it.
Now my days are numbered — okay, everyone’s days are numbered, but I suspect my number is lower than most — and I’ve pondered the possibility of porting my Main Site, which is largely WordPress but self-hosted, over here at some point, mainly because I can’t reasonably expect my descendants to maintain (and pay for) that site. About 8,000 items that aren’t in a WordPress environment would of necessity have to be sacrificed. Still, that leaves about 14,000 posts and a handful of pages, which could be done in — well, last time I had to do an import into WordPress, it took about a week for about a third as much material.
And of those three gigabytes, I’d use up two pretty quick. Then again, it’s not like I expect to make a whole lot of posthumous posts.
I was commiserating with friends and acquaintances hosted with Bluehost and Hostgator and such, many of whom were having ongoing problems with their sites, when my own operation suddenly grinds to a screeching halt. Is someone trying to tell me something? (And does this have anything to do with WordPress 3.6, which I installed this morning on four sites?)
About 3 pm, all my sites (except this one) went down; I went to turn in a trouble ticket, and was informed that “other customers had reported similar issues,” which tells me that a whole bank of servers has probably gone south. We shall see.
Just when you thought the return of Serge Ibaka’s shooting mojo might save the day, the Thunder fell back into their “Do we have to have a third quarter?” funk, and an erstwhile 17-point lead was vaporized. It was tied at 76 at the beginning of the final frame, and when Kevin Durant missed a layup (!) at 2:55, things began to unravel. The Grizzlies were up 94-92 with ten seconds left, and everyone knew Durant would be getting the ball on the next possession. KD, undaunted, pushed to the rim for the layup to tie it. The Griz had six seconds left; Zach Randolph went up for the win, and Kendrick Perkins swatted it away. Welcome to overtime. The Thunder didn’t even score in the bonus period until 1:55, when Derek Fisher made his first trey of the night, at which time it was 98-97 Memphis. “Dripping with drama,” said radio guy Matt Pinto. Durant’s subsequent pullup jumper was rather drippy itself, and Mike Conley delivered a nifty pass to Marc Gasol to put the Griz up by three. Gasol subsequently added a free throw to make it 101-97, and Pinto and Grant Long got to complain about a call while Lionel Hollis plotted the Thunder’s demise. It was Tayshaun Prince, arguably the poorest of the Memphis free-throw shooters, who finished the job with two more, to put the Griz up six (again!), 103-97.
Which means that Wednesday could be the end of it all, especially if the Bears keep coming up with double-figure performances like Gasol’s (23 points, 11 rebounds), Z-Bo’s (23 points, 12 rebounds), and Conley’s (team-high 24). OKC registered some reasonable figures, but when Durant’s game-high 27 ends up -7, it’s a lost cause.
Besides, the Heat barbecued the Bulls, 88-65, to go 3-1 in that race. Suddenly I am very, very tired.
But at least we have an explanation of sorts now:
[T]he connectivity issues are due to large-scale brute force attacks to wp-login pages. These attacks are overloading affected servers and the fix being applied will limit the rate these attacks are hitting wp-login pages. In addition to the fix that’s being applied everywhere, we’re also mitigating the attack by blocking IP addresses all around our data centers.
WordPress.com users are presumably already protected from this vandalism.