[closed] The api.fanout.io domain is not always resolving. We are investigating the issue.

Our DNS provider is failing to respond in certain regions.

Our DNS provider has made a fix and we are monitoring the situation.

[closed] Fanout domain names including fanout.io and fanoutcdn.com may not be resolving. We are investigating the issue.

Our DNS provider has fixed the issue, and we are monitoring the situation.

This incident has been resolved.

[closed] Fanout domain names including fanout.io and fanoutcdn.com may not be resolving. We are investigating the issue.

Our DNS provider has acknowledged higher than normal errors.

Our DNS provider is still working on the issue.

The issue has been fixed and we are monitoring it.

This incident has been resolved.

[closed] It was discovered that messages were not being delivered for a subset of Bayeux channels in the SF region. This has been resolved.

[closed] Requests to our internal DNS provider are delayed or failing, causing degraded service. The issue is being investigated.

[closed] This incident has been resolved.

[closed] Within the past hour, some message deliveries were failing in our London region. This has been resolved.

[closed] We will be undergoing scheduled maintenance during this time.

Scheduled maintenance is currently in progress. We will provide updates as necessary.

The scheduled maintenance has been completed.

[closed] For the past several hours, many messages originating at our SF region were failing to dispatch. This has been resolved.

[closed] Over the past three hours, not all messages published to our SF region propagated to our London region. This has now been resolved.