CheckUpstream measured 100ms at 100.000% availability across 2030 independent checks (global · api). 2 incidents were recorded in the past 12 months; the most recent resolved 18 days ago after 3 hours. Status signals are polled from 100ms's official Atlassian Statuspage status page, alongside independent probes and community reports.
Share of our own checks against 100ms endpoints that returned 100ms's expected response. Evidence that their API edge is answering correctly — not that every product behind it works.
Vendor disclosed: 2 incidents · 362 of 365 days with none posted · 4h 33m of declared impact
Fewer incidents in the last 30 days than 45% of 232 tracked services.
Share of each window with no impact declared by 100ms
7d
100.000%
30d
99.574%
90d
99.858%
180d
99.895%
1y
99.948%
Downtime like this can be refundable
If you're a paying 100ms customer, outages in these windows may count against 100ms's SLA — vendors owe service credits for missed uptime targets, but only if you file inside the deadline. CheckUpstream tracks the entitlement, drafts the claim, and hands you the filing link.
A 100ms outage only matters if something you ship depends on it. Point us at a public repository and we will read its dependencies and tell you — no account, nothing stored.
GitHub READMEs, GitLab, MDX docs — links to the live reliability page.
Frequently Asked Questions
›Is 100ms currently down?
100ms is currently Operational. CheckUpstream tracks 100ms in real-time across the official status page, RSS / Atom feeds, and community telemetry. Refresh this page for the latest reading.
›When did 100ms last have an outage?
100ms's last resolved incident started 18 days ago and lasted 3h 4m (a complete outage).
100ms's 30-day measured availability is 100.000%, from CheckUpstream's own probes against 100ms endpoints. It is the share of checks that returned the expected response, not a figure taken from 100ms's status page.
›How do I monitor 100ms in production?
Sign up to CheckUpstream and add 100ms to a watchlist. We send incident alerts via Slack, email, webhook, or PagerDuty within seconds of detection, covering both the official status page and community signals (HN, Reddit, Bluesky, Cloudflare Radar).
›How does CheckUpstream track 100ms?
We poll 100ms's official status page on a 1-5 minute cadence, parse its RSS / Atom feed as a fallback, ingest community signals from social platforms, and aggregate per-org SDK telemetry. Multiple sources reduce false positives versus any single feed alone.