Network status

Incident history

Every incident and maintenance window since the network went live in June 2011: 15 entries, newest first. Problems with a single relay are recorded on that relay’s page.

2026

  1. · East Asia · Resolved

    Delayed message delivery in East Asia

    A relay in our Chiba data center failed during a routine restart. Traffic was rerouted automatically, and messages were delivered late but intact.

    Degraded performance · Duration: 47 minutes

  2. · All regions · In progress

    Calibrations begun

    Our Chief Technology Officer has begun calibrating the relay network. We will update this notice when calibrations are complete. Posted by Dr. Pasqal Haneumann.

    Notice · Duration: Ongoing

  3. · All regions · Completed

    Scheduled relay maintenance

    Planned maintenance on the relay network ahead of the Glossia 4.0 release. Messages queued during the window were delivered when it ended.

    Maintenance · Duration: 2 hours

  4. · All regions · Resolved

    Relay directory published late

    A software fault in the signing service delayed three hourly directories. Clients kept using the previous directory, and delivery was not affected.

    Notice · Duration: 3 hours 5 minutes

2025

  1. · South and Southeast Asia · Resolved

    Slow delivery in South and Southeast Asia

    A routing error at an upstream network provider in Mumbai sent traffic for several relays the long way around.

    Degraded performance · Duration: 1 hour 25 minutes

  2. · Europe · Resolved

    Connection flood against entry relays in Europe

    Entry relays in Europe received a flood of connection attempts. Clients moved to less loaded relays and delivery slowed by a few seconds.

    Degraded performance · Duration: 3 hours 40 minutes

2024

  1. · Africa · Resolved

    Slow delivery in West Africa after subsea cable damage

    Damage to several subsea cables off the coast of West Africa cut or slowed international connections across the region.

    Degraded performance · Duration: 6 days

2023

  1. · All regions · Resolved

    New installations could not connect

    A certificate used to publish the relay directory expired at midnight. Existing clients kept working; new installations could not connect.

    Outage · Duration: 2 hours 50 minutes

2022

  1. · All regions · Completed

    Glossia 3.0 upgrade window

    Frothly relays moved to relay software 3.0. Messages were held during the window and delivered when it ended.

    Maintenance · Duration: 3 hours

2020

  1. · All regions · Resolved

    Slower delivery during a surge in traffic

    Traffic grew by more than half in three weeks. Delivery slowed at busy hours until new capacity was added.

    Degraded performance · Duration: 9 days

2019

  1. · East Asia · Resolved

    Slow delivery in East Asia after Typhoon Faxai

    Typhoon Faxai cut power across much of Chiba Prefecture. Frothly’s Chiba relays ran on generators, and an upstream network outage slowed delivery in East Asia.

    Degraded performance · Duration: 6 hours 20 minutes

2018

  1. · Middle East and Central Asia · Resolved

    Entry relays blocked by a national network operator

    A national network operator began blocking every listed entry relay. Clients in the country switched to bridges.

    Degraded performance · Duration: 4 hours

2014

  1. · All regions · Completed

    Glossia 2.0 upgrade window

    The network moved to relay software 2.0, which introduced mailbox relays and the hourly signed directory.

    Maintenance · Duration: 4 hours

  2. · All regions · Completed

    Relay transport keys replaced

    After a serious vulnerability was disclosed in a widely used encryption library, every relay replaced its transport keys.

    Maintenance · Duration: 6 hours

2012

  1. · All regions · Resolved

    Relays stopped forwarding after a leap second

    A leap second added at midnight UTC caused relays to stop forwarding messages until they were restarted.

    Outage · Duration: 1 hour 50 minutes