StatusDetector

Live intelligence

Shutdown Radar

Real-time view of services going dark — active outages, products retired this month, sunset announcements with countdowns, and the shutdown archive. One screen.

ScanningLast checked 02:34 AM UTCAuto-refresh every 1 min

Major / Critical

0

Degraded

1

Sunsetting

2

Archived

30

Currently degraded or down

1 active · cross-referenced from official feeds and our probes

Auto-refresh 1 min

Recent shutdown records

Verified shutdowns from the past 12 months, newest first. 3 archived.

Mozilla Pocket

Retired by Mozilla

352d ago

Read-later service Mozilla acquired in 2017, built into Firefox.

Mozilla is "redirecting resources" to focus on Firefox and AI features.

Retired Jul 8, 2025Source

Skype

Retired by Microsoft

416d ago

The video and voice calling service Microsoft bought in 2011 for $8.5B.

Microsoft is consolidating consumer chat into Teams.

Retired May 5, 2025Source

TinyLetter

Retired by Mailchimp / Intuit

481d ago

Mailchimp's free, simple personal newsletter tool, beloved by writers.

Mailchimp redirected users to its main product after Intuit's acquisition.

Retired Mar 1, 2025Source

Sunsetting soon

Verified end-of-life announcements with first-party sources.

2 confirmed

Shutdown archive preview

A curated record of retired services. The full archive keeps the memorial voice.

Frequently asked

Common questions about how the radar is built and what each section means.

What's the difference between Active outages, Recent shutdown records, and Sunsetting soon?

Three distinct things. Active outages are services that are degraded or down right now — sourced from vendor status feeds and our HTTP probes. Recent shutdown records are services that were permanently retired in the past 12 months — these are historical, with sources cited. Sunsetting soon is a calendar of products with publicly announced end-of-life dates in the future, with a countdown so you have time to migrate.

How do you know a service is sunsetting?

Every entry in the sunsetting and graveyard sections is verified against a first-party source before it appears here — the vendor's own blog post, a status-page announcement, an SEC filing, or a support article. We don't aggregate unverified rumour. The "Source" link on each card opens the underlying announcement.

Why does an active incident sometimes disappear from the list?

Incidents drop off the live feed as soon as both the vendor's status feed reports resolution AND our probe sees consistent healthy responses. The radar is the real-time view; for a chronological list of resolved incidents see /outages, or open a specific service to see its 90-day history.

Source verification. Every active incident is cross-referenced against the vendor’s own status feed or our HTTP/SSL probe. Each retired service and sunset announcement is verified against a first-party source — vendor blog post, status page, or support article — before it appears here. Hover or tap any “Source” link to open the underlying record. Full methodology