Miami-b01 Reboot

We hit a Xen bug on Miami-b01 and had to reboot it. All Webbies Webbies should be up and running now.

If you have any questions, please get in touch with our support team. Thanks

Power failure for switching system: mia-a facility

8:00AM GMT: A power circuit that powers on some of our main switches crashed. Due to this issue we experienced a network interruption for a big portion of MIA-A, this included the Webbynode site, as well as Webby Manager. Plese note all the Webbies remained up even if not accessible, the issue was directly to the switching gear. We brought up the main power circuit back, and we’re now 100% back. MIA-B Webbies were not affected by this incident. We are investigating why the 2nd failover power circuit did not take over, to ensure this situation doesn’t repeat itself.

8:45AM GMT: We’re now back up. Please contact support if you’re experiencing any further issues.

Webby Manager and miami-b01 network maintenance

4:10AM GMT: We are currently performing a maintenance on Webby Manager network, and connectivity from manager to miami-b01 node is affected. All Webbies remain up and running.

CURRENT AFFECTED SERVICES: Webby Manager, API, New Customer Signups, Redeployments, are all experiencing slowness and/or unavailability.

WEBBIES ARE UP AND RUNNING.

Ajaxterm Console Maintenance

3:30PM GMT: We’re doing some maintenance/changes to The Ajaxterm web console. Please use SSH (PuTTy for windows) in order to manage your Webbies during this time.

CURRENT AFFECTED SERVICES: Ajaxterm Web Based Console

WEBBIES ARE UP AND RUNNING.

Resolved – Webby Manager problems

9:30PM GMT: We’re experiencing problems with Webby Manager. We’re actively working on it.

CURRENT AFFECTED SERVICES: Webby Manager, API, New Customer Signups, Redeployments, are all experiencing slowness. WEBBIES ARE UP AND RUNNING.

Update 9:57PM GMT: Manager is now back up, we ran into a bad batch of ram for the Manager’s system. We’re back online. All Webbies remained online, and there was no downtime.

Resolved – DDoS Attack

We are experiencing high server loads on Webby Manager due to a current DDoS attack. We are actively trying to mitigate the problem and will keep you informed.

CURRENT AFFECTED SERVICES: Webby Manager, API, New Customer Signups, Redeployments, are all experiencing slowness. WEBBIES ARE UP AND RUNNING.

If you have any questions, please get in touch with our support team. Thanks!

Update 1:30PM EST: we had to move all Webbies out of miami-a05. This migration was completed with no data loss.

Emergency restart miami-a05

We’ve hit a Xen bug on Miami-a05, we are rebooting the server and all Webbies should come back shortly.

Update: All Webbies are now up and running.

If you experience any further issues please send us a ticket.

Webby Manager Maintenance

This maintenance will result in a performance improvement, as we will be adding more hardware resources to the Webby Manager system.

DATE: Monday July 7th @ 10:30 PM EST

DURATION: 45mins – 60mins

SERVICE INTERRUPTION: Webby Manager, API, New Customer Signups, Redeployments, all will be un available during the maintenance window. ALL WEBBIES WILL REMAIN ONLINE.

If you have any questions, please get in touch with our support team. Thanks!

Update: Maintenance has been completed, the Webby Manager is now back live.

Resolved – Payment Gateway down.

Hello everyone,

We have been having issues processing new orders today, as Authorize.net as has been down for a few hours at this time. We have not received any official notification of what has happened.

At the time, no CC payments can be processed, however you may use Paypal as a sign up option.

We will update this ticket as soon as we hear from Authorize.net

Update 4:00pm EST: Authorize.net is back up and, being so, we can again process Credit Cards.

System Notice: Unscheduled Network Interruption

Incident: Intermittent network interruption.
Time: From 3:00AM – 6:AM EST.
Reason: Carrier Issues

Hello,

This morning, we received a notice that our main datacenter had to go through a unplanned network maintenance with one of the network carriers. However, it wasn’t a total 100% downtime, due to the fact that some carries still had access.

During this process however, some internal Cisco errors came up which caused further complications within our OSPF/BGP routing tables that were fixed already.

I would like to extend my personal apologies to you for the instability of our network during this timeframe. We value your business and are working diligently to see how situations like this can be prevented in the future.

Please contact our Helpdesk if you are still experiencing any network issues.