Nexus Bytes System Heart Beat - Notice history

All systems operational

Ever wondered if we are alive? Come check out our heartbeat!

LA - Operational

100% - uptime
Aug 2020 · 100.0%Sep · 100.0%Oct · 99.60%

Previous page

Next page

Aug 2020
Sep 2020
Oct 2020

London - Operational

100% - uptime
Aug 2020 · 100.0%Sep · 100.0%Oct · 100.0%

Previous page

Next page

Aug 2020
Sep 2020
Oct 2020

Germany - Operational

99% - uptime
Aug 2020 · 100.0%Sep · 100.0%Oct · 99.05%

Previous page

Next page

Aug 2020
Sep 2020
Oct 2020

Miami - Operational

100% - uptime
Aug 2020 · 100.0%Sep · 100.0%Oct · 100.0%

Previous page

Next page

Aug 2020
Sep 2020
Oct 2020

NYC - Operational

100% - uptime
Aug 2020 · 100.0%Sep · 100.0%Oct · 100.0%

Previous page

Next page

Aug 2020
Sep 2020
Oct 2020

Japan - Operational

100% - uptime
Aug 2020 · 100.0%Sep · 100.0%Oct · 100.0%

Previous page

Next page

Aug 2020
Sep 2020
Oct 2020

Singapore - Operational

100% - uptime
Aug 2020 · 100.0%Sep · 100.0%Oct · 100.0%

Previous page

Next page

Aug 2020
Sep 2020
Oct 2020

Netherlands - Operational

100% - uptime
Aug 2020 · 100.0%Sep · 100.0%Oct · 100.0%

Previous page

Next page

Aug 2020
Sep 2020
Oct 2020

Melbourne - Operational

100% - uptime
Aug 2020 · 100.0%Sep · 100.0%Oct · 100.0%

Previous page

Next page

Aug 2020
Sep 2020
Oct 2020

Notice history

Oct 2020

Germany is inaccessible at the moment (automated)
  • Resolved
    Resolved

    Germany is now operational! This update was created by an automated monitoring service.

  • Identified
    Identified

    We have identified the root cause. An official announcement will be sent out shortly.

    Only Gervm5 hostnode was affected.

  • Resolved
    Resolved

    Germany is now operational! This update was created by an automated monitoring service.

  • Investigating
    Investigating

    We are currently investigating this incident.

  • Identified
    Identified

    Germany cannot be accessed at the moment. This incident was created by an automated monitoring service.

Gerhvm2 -outage
  • Resolved
    Resolved

    We just resolved the issue! Faulty memory module has been replaced.

  • Identified
    Identified

    We are currently investigating this incident.

    • Faulty memory detected. Being replaced.
LAHVM1 is inaccessible at the moment (automated)
  • Resolved
    Resolved

    Hard drive has been replaced. Raid rebuild is in progress.

  • Update
    Update

    LAHVM1 (Storage node) suffered 2 disk failure. We are working on getting them replaced.

  • Identified
    Identified

    LA cannot be accessed at the moment. This incident was created by an automated monitoring service.

Sep 2020

No notices reported this month

Aug 2020

No notices reported this month

Aug 2020 to Oct 2020

Next