[Done] Scheduled maintenance on Web228, April 3rd, 2014.

Posted in Scheduled downtime by

Web228 will be taken down Thursday April 3rd, 2014 for a HDD cable swap and RAID firmware upgrade. The downtime should be within 2 hours. We will update this post as maintenance will progress.

2014-04-03 09:03 UTC The maintenance is starting now.

2014-04-03 09:48 UTC Cables have been swapped, now performing the RAID firmware upgrade.

2014-04-03 10:28 UTC While doing the upgrade we found issues on the RAID card and is going to be swapped.

2014-04-03 12:39 UTC The server is back to operational status.


[Done] PostgreSQL upgrade on Web22,Web23,Web223 and Web228

Posted in Scheduled downtime by

We are going to upgrade Postgresql 8.3 / PostGIS 1.3.6 to Postgresql 8.4 / PostGIS 1.5 on the following servers in the

upgrade interval mentioned alongside.

Web22    May 5, 2am to 4am UTC

Web228  May 5, 3am to 5am UTC

Web223  May 5, 4am to 6am UTC

Web23    May 5, 5am to 7am UTC

Postgresql will be unavailable for the duration of the upgrade.

We will update this post as the upgrades progress.

[May  5 03:09 UTC] The upgrade on Web22 is over.

[May  5 04:46 UTC] The upgrade on web223 is over while Web228 is still going on due to the large amount of data.

[May  5 05:20 UTC] The upgrade on Web228 is over.

[May  5 06:50 UTC] The upgrade on web23 is over.


[Fixed] Intermittent network routing issues affecting several US servers

Posted in Problems by

Several of our US servers are currently experiencing intermittent network routing issues. Affected servers may include: Dweb100 Dweb101 Dweb102 Dweb104 Dweb105 Dweb110 Dweb111 Dweb112 Dweb113 Dweb114 Dweb115 Dweb116 Dweb117 Dweb118 Dweb119 Dweb120 Dweb121 Dweb122 Dweb123 Dweb124 Dweb125 Dweb126 Dweb127 Dweb128 Dweb129 Dweb130 Dweb133 Dweb134 Dweb135 Dweb137 Dweb140 Dweb141 Dweb142 Dweb143 Dweb144 Dweb145 Dweb146 Dweb147 Dweb149 Dweb150 Dweb151 Dweb152 Dweb153 Dweb154 Dweb158 Dweb160 Dweb161 Dweb162 Dweb163 Dweb164 Dweb91 Dweb92 Dweb93 Dweb94 Dweb95 Dweb96 Dweb97 Mailbox8 Web102 Web105 Web106 Web108 Web11 Web114 Web117 Web119 Web12 Web122 Web126 Web129 Web143 Web148 Web15 Web151 Web155 Web162 Web174 Web175 Web178 Web180 Web182 Web183 Web186 Web187 Web198 Web199 Web200 Web213 Web219 Web220 Web226 Web227 Web228 Web229 Web230 Web231 Web232 Web233 Web234 Web235 Web236 Web237 Web238 Web239 Web24 Web240 Web241 Web243 Web244 Web245 Web246 Web247 Web25 Web27 Web28 Web30 Web300 Web301 Web302 Web307 Web308 Web309 Web31 Web310 Web311 Web312 Web313 Web318 Web319 Web320 Web324 Web328 Web329 Web330 Web335 Web336 Web337 Web338 Web34 Web341 Web342 Web343 Web344 Web345 Web346 Web347 Web348 Web349 Web35 Web37 Web39 Web4 Web40 Web42 Web48 Web49 Web5 Web55 Web57 Web65 Web69 Web70 Web72 Web74 Web75 Web80 Web83 Web91 Web95 Web99

We’re working to resolve this issue and will update this post when we have more information.

2012-10-15 6:07 UTC: The problem was an issue with an upstream network carrier and has been resolved.