Instatus - Notice history

Under maintenance

Public status pages - Under maintenance

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

Previous page

Next page

Aug 2020100.0% uptime
Sep 2020100.0% uptime
Oct 2020100.0% uptime

Private status pages - Under maintenance

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

Previous page

Next page

Aug 2020100.0% uptime
Sep 2020100.0% uptime
Oct 2020100.0% uptime

Dashboard - Under maintenance

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

Previous page

Next page

Aug 2020100.0% uptime
Sep 2020100.0% uptime
Oct 2020100.0% uptime

API - Under maintenance

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

Previous page

Next page

Aug 2020100.0% uptime
Sep 2020100.0% uptime
Oct 2020100.0% uptime

Maintenance Automations - Under maintenance

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

Previous page

Next page

Aug 2020100.0% uptime
Sep 2020100.0% uptime
Oct 2020100.0% uptime

Integrations - Under maintenance

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

Previous page

Next page

Aug 2020100.0% uptime
Sep 2020100.0% uptime
Oct 202099.80% uptime

Notice history

Oct 2020

There is an issue with receiving automated incidents
  • Resolved
    Resolved

    Mailgun has resolved the issue earlier. Apps should work as expected now!

  • Monitoring
    Monitoring

    Mailgun has resolved the issue and monitoring the situation.

    Instatus automation is now working, but I'm waiting for Mailgun to close the issue, so that I can close it too!

  • Update
    Update

    Mailgun has added the issue to their status page. Currently waiting for them to resolve the issue.

  • Identified
    Identified

    There is an issue with receiving automated incidents using emails *@automation.instatus.com. I opened a ticket with Mailgun to resolve the issue, and waiting for their response.

Sep 2020

No notices reported this month

Aug 2020

There is an issue with receiving automation requests
  • Resolved
    Resolved

    We just resolved the issue!

  • Identified
    Identified

    We are continuing to work on a fix for this incident.

Aug 2020 to Oct 2020

Next