Vendor record
100ms
Checked
Front door check counts and 100ms’s own incident posts. Use them to investigate a dependency; neither confirms what happened in your app.
Front door checks
We send a request to a documented 100ms endpoint and count the checks that got the answer it is documented to give.
Front door reachable in 2,879 of 2,879 checks with a clear answer, last 30 days, checked every 15 minutes from a single CheckUpstream location.
- Endpoint checked
- api.100ms.live
- Scope
- apiNo vendor region
- First check in this window
- Latest clear answer
Checks 15 minutes apart cannot see disruptions shorter than that. A check that reached the front door does not show that every 100ms product, region or your app worked.
How we count front door checks100ms says
Incident posts from 100ms’s status page, with its titles, impact levels and times. They say what 100ms chose to post, not what reached your app.
A closed record shows when our record closed. Some older records closed when a post left the status page, without a resolution post from the vendor.
0
incidents 100ms posted, last 7 days
Most recent records · all dates
India region is facing issue for conferencing, streaming and recording
Critical100ms’s postStarted, per 100ms
Closed in our record(3h 4m)
Conferencing services are not working
Critical100ms’s postStarted, per 100ms
Closed in our record(1h 29m)
Your code, your dependencies
See which of your code paths call 100ms
Connect GitHub or GitLab to find where your public or private repository uses 100ms. Review each match and your alert settings.
Free to start. No credit card.
Use this record on your site
Add 100ms status to your page.
Choose the format your page supports, then copy the code. Badges show the recorded vendor status; they do not establish impact on your app.
Frequently Asked Questions
Is 100ms currently down?
100ms's latest recorded status is Operational. Check the timestamp and linked source at the top of this page. A vendor status report does not establish whether your application was affected.
When did 100ms last have an outage?
The most recent closed incident record began 64 days ago and spans 3h 4m. The vendor reported a complete outage. Closure may reflect a disappeared post or an expired tracking period; it does not confirm vendor or application recovery. Check the dated history and source links.
Does CheckUpstream publish an uptime percentage for 100ms?
No. CheckUpstream checks 100ms’s front door every 15 minutes and publishes how many checks reached it over the last 30 days, with the endpoint checked. Checks 15 minutes apart cannot see disruptions shorter than that. A percentage would claim more than the checks can show.
How do I monitor 100ms in production?
Create your account, connect GitHub or GitLab and choose a public or private repository. Review the vendor matches and your alert settings. Available notification channels and history depend on your plan.
How does CheckUpstream track 100ms?
This record separates vendor-reported incidents from independent checks. Sources and coverage vary by vendor: review the linked source, check time and measurement scope. Neither kind of evidence establishes SLA credit eligibility.