Previous incidents

Our SNAM location is facing a partial outage, a backup provider is online to serve new links.

Please note links that were generated and being served from the provider facing an outage will need to be regenerated once they expire to point to the backup provider.

Further updates to follow.

UPDATE: Service has been restored. We apologise for the brief outage.

The team is aware of a general outage affecting the service. We apologize for the inconvenience.

We've enabled a fallback path for APAC due to network instability in the region.

Resolved.

We're seeing connectivity issues between some backend assets. Transcoding and certain file retrievals are degraded.

We're looking into it

We're looking into reports of API availability issues

We fired the guy responsible, we're so back

Our upstream is busy tuning our WEUR attack mitigation profile. We apologise for the delay in notice.

Services will be restored shortly.

We have deployed additional capacity. New links generated on WEUR will automatically route to the new servers. If you are still experiencing issues, try swapping to a different region and restarting your device.

We're seeing higher than normal rates of errors returned by the API and the team is investigating.

We're responding to a large network event. Expect periodic waves of service instability.

Progress is being made, we will continue to publish relevant updates as they occur.

Resolved API issues. Apologies for the inconvenience.

We're investigating an upstream outage in our Miami region

EDIT: We're seeing region restoration

Our NORD CDN is having some troubles and we're working on it

EDIT: Restored, we apologise for that short outage.

EDIT: Still seeing sporadic periods of high loss. NORD will remain disabled for the time being.

We're seeing database related API timeouts.

EDIT: Resolved.

This issue has now been resolved. We appreciate your patience as we scale up to meet demand. Thank you.

We're seeing sporadic loss within Akamai's network into Mumbai. We have alerted our upstream provider for further details.

The affected path has been isolated and avoided. We're continuing to monitor.