MailPace incident

Blog is down

Resolved after 1 hour 44 minutes, affecting Blog, on May 10, 2026.

investigating May 10, 2026, 06:47 AM UTC

In [`3948d66`](https://github.com/mailpace/status/commit/3948d661a65ffc038a8162dbfff4c1b97476a908 ), Blog (https://blog.mailpace.com) was **down**: - HTTP code: 0 - Response time: 0 ms

Started: May 10, 2026, 06:47 AM UTC
Resolved: May 10, 2026, 08:31 AM UTC
Duration: 1h 44m
Detected by Pingoru: May 10, 2026, 06:47 AM UTC

Affected components

Blog

Update timeline

investigating May 10, 2026, 06:47 AM UTC

In [`3948d66`](https://github.com/mailpace/status/commit/3948d661a65ffc038a8162dbfff4c1b97476a908 ), Blog (https://blog.mailpace.com) was **down**: - HTTP code: 0 - Response time: 0 ms

Your product runs on more than MailPace

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.