We have been informed that the dotmobi (.mobi) registry will be conducting maintenance on July 4th between 1500 and 1900 UTC

Existing .mobi domains will not be affected

Updates and new registrations will not be available
The Linux webserver pemlinweb04 is currently experiencing performance issues.

Our technical support team are aware of the situation and are currently investigating it.

Update: 2359 This issue appears to have been resolved


Today we've put wordpress 2.8-5 into the app vault for you all to upgrade to and all new installs should use this.

If you follow the below steps you should be safe and encounter few if any problems:

1) Backup your files and databases before performing this upgrade.
2) Disable all custom plugins before upgrading also
3) upgrade via the app vault
4) re-enable plugins 1 by 1

Please let us know how you get on with this. All feedback is welcome.
The .be registry (dns.be) is conducting some scheduled maintenance this afternoon from 5pm onwards.

The expected timeframe is about 10 minutes.

This will only impact new .be domain registrations being processed
Our main website is currently under attack. We're working to mitigate this attack at the moment and hope to have our site back online shortly.

We'll post further updates when we have them.

Update: 20:30

This attack is on-going, our site may be available to some people and not to others. We're working on a resolution currently. We hope to resolve this issue in the next 24 hours.

Update: June 9th 08:15

This DDOS continued for 4 days solid. We did however keep our site online for the duration and I'll write up some notes on how we did this in the not too distant future.
At approximately 2pm this afternoon one of the power strips in one of our cabinets in Interxion "tripped".

As most of the servers in the rack are either dual powered or using the other side's PDU the issue wasn't spotted immediately.

Once the issue was identified the data centre staff reset the trip and power was restored.

All affected clients have been contacted or attempted to be contacted.


Reblog this post [with Zemanta]

Server Upgrades

TrackBacks (0) Comments (0)
The following servers will be rebooted between 6:00 and 7:00 am on Thursday May 28th.

pemlinweb01 through pemlinweb12

This is to facilitate some memory upgrades due to spikes in activity during peak hours. We'll be doing them in batches starting with:

pemlinweb01.blacknight.com
pemlinweb03.blacknight.com
pemlinweb05.blacknight.com
pemlinweb10.blacknight.com

then:

pemlinweb02.blacknight.com
pemlinweb04.blacknight.com
pemlinweb06.blacknight.com
pemlinweb11.blacknight.com

then:

pemlinweb07.blacknight.com
pemlinweb08.blacknight.com
pemlinweb09.blacknight.com
pemlinweb12.blacknight.com

The reboots should be quite quick as the memory install should only take 30 seconds per node.

If you have any issues after 07:00 on the 28th please contact support immediately.

NB: All times are Dublin, Ireland. This service notice only affects shared servers. It has no impact on VPS servers

Update: 07:00

Phase 1 and 2 complete with all nodes back online. An unforeseen set back has delayed the startup of pemlinweb7/8/9/12. Once an fsck is done on these machines they should be back up. It's around 25% of the way done. We estimate that they'll be back by approx 07:30. I'll post further updates shortly. This maintenance window has been extended for another hour as a precaution.

Update: 07:35

Those machines are now back online. This maintenance window is now completed and closed.
We experienced an issue today where one of our transit routers had an issue due to the carriers router flapping it's bgp session. We've shut down this BGP session and had a conversation with the carrier about the issue. While bgp was doing it's thing, some people may have noticed some latency or slowness to connect. This was due to the routes moving from 1 ISP to the other.

Currently Global Cross and Cogent are carrying our traffic. Level(3) are out of the picture for the moment.

Further updates will be posted as we have them.

Update: 17:05

Packet Exchange have acknowledged an issue on their network. One of their customers was advertising the Level(3) router IP into the same VLAN we're in. So Level(3) and this other customer were fighting for the IP. This session is still down.

As an interim measure to ensure we continue to offer the same high level of service that our customers are used to we're putting Tiscali back into the loop. So we'll be back to 3 live carriers. This is happening now and Tiscali should be starting to take traffic away from Cogent and Global Crossing.

Further updates will be posted until this issue is resolved.

Update: 14:55 May 21st

Packet Exchange report that this issue is resolved. We've also received an RFO. With this in mind we'll be turning Level(3) back up at 18:30 this evening. This will cause some brief latency while routes re-converge. A final update will be posted once our engineering team confirm everything is ok once we bring this circuit back up.

Update: 20:30 May 21st

Level(3) has been live for the past 2 hours and all is looking well. This is the last update on this particular ticket. We're closing it now.
The shared, DirectAdmin, server "Ragnell" is currently experiencing issues.

Our technical team are working on a resolution.

This notification only affects sites on that server.

UPDATE: 1940 As the server is unresponsive a reboot is required.

UPDATE: 2027 Service was fully restored a few minutes ago.


At around 14:40 today we began to notice a slow down in connections to parts of our firewalled network in the InterXion data centre.  This can affect any of our new shared hosting plans, VPS plans, and some dedicated and colocated equipment.

Our engineers are working on what may be causing the network congestion and the symptoms range from either a slow connection to your website, VPS, or server, or a temporary loss in connection entirely. 

This is not affecting all services in this data centre and it is not a total loss of connectivity, there is just congestion that is slowing down the traffic into some parts of the firewalled network that protect the above systems.