User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
msasafety.com · Cloud & developer
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses. Every report with a known place can appear on the map. Updates every minute.
Each row is a time, a coarse place, and a problem type from a new report. Optional notes stay private. Places with fewer than 3 reports in the last 8 days are shown without a location.
No public reports yet.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last checked 2 hr ago. Last stored result reached it in 424 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Nov 6 | 0 | 0.0 | 380 ms | 0 |
| Nov 7 | 0 | 0.0 | 400 ms | 0 |
| Nov 7 | 0 | 0.0 | 355 ms | 0 |
| Nov 7 | 0 | 0.0 | 348 ms | 0 |
| Nov 7 | 0 | 0.0 | 413 ms | 0 |
| Nov 8 | 0 | 0.0 | 364 ms | 0 |
| Nov 8 | 0 | 0.0 | 369 ms | 0 |
| Nov 8 | 0 | 0.0 | 365 ms | 0 |
| Nov 8 | 0 | 0.0 | 386 ms | 0 |
| Nov 9 | 0 | 0.0 | 371 ms | 0 |
| Nov 9 | 0 | 0.0 | 340 ms | 0 |
| Nov 9 | 0 | 0.0 | 332 ms | 0 |
| Nov 9 | 0 | 0.0 | 365 ms | 0 |
| Nov 10 | 0 | 0.0 | 390 ms | 0 |
| Nov 10 | 0 | 0.0 | 436 ms | 0 |
| Nov 10 | 0 | 0.0 | 406 ms | 0 |
| Nov 10 | 0 | 0.0 | 366 ms | 0 |
| Nov 11 | 0 | 0.0 | 388 ms | 0 |
| Nov 11 | 0 | 0.0 | 329 ms | 0 |
| Nov 11 | 0 | 0.0 | 381 ms | 0 |
| Nov 11 | 0 | 0.0 | 416 ms | 0 |
| Nov 12 | 0 | 0.0 | 413 ms | 0 |
| Nov 12 | 0 | 0.0 | 348 ms | 0 |
| Nov 12 | 0 | 0.0 | 424 ms | 0 |
| Nov 12 | 0 | 0.0 | 413 ms | 0 |
| Nov 13 | 0 | 0.0 | 407 ms | 3 |
| Nov 13 | 0 | 0.0 | 339 ms | 2 |
| Nov 13 | 0 | 0.0 | 407 ms | 0 |
| Nov 13 | 0 | 0.0 | 414 ms | 0 |
| Nov 14 | 0 | 0.0 | 312 ms | 0 |
| Nov 14 | 0 | 0.0 | 431 ms | 0 |
94.05% uptime · No user reports in the last 24h
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 9 days of data so far, so the 90-day numbers fill in over time.
One report per service every 10 minutes from this network. No account.
Get an email when MSA Safety goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send MSA Safety alerts to Slack, Discord or a webhook — free.
MSA Safety, at msasafety.com, is one of the Cloud & developer services we monitor. MSA Safety is a global organization commited to developing, manufacturing and supplying safety products to help protect people and facilities.
MSA Safety publishes an official status page at status.msasafety.com; when we can read it, its incident level is folded into the status shown here.
Common problems for cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
Measured uptime from our checks: 94.05% over 9 days of checks. We logged 2 public incidents since monitoring began 9 days ago.
Response time over the last 24 hours: 391 ms average, 303–487 ms range across 13 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
The most recent public incident we recorded started 2026-11-13 and lasted 2 h. 2 incidents since monitoring began 9 days ago.
From our own checks: 94.05% over 9 days of checks.
391 ms on average over the last 24 hours (303–487 ms).
Yes, at https://status.msasafety.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For cloud & developer services, watch for API errors, failed deploys or builds, and dashboard or console outages. If many people report MSA Safety here at once, the problem is on MSA Safety's side.
How we detect and verify outages · Dispute this report · We review disputes within 24 hours.
Community comments
Share what you are seeing with MSA Safety. No account needed. Comments are public, separate from outage reports. Do not include personal information.
No links or domains. 3 comments per service and 6 total per hour, per device and network. New contributors get one visible comment; further comments wait for review.