User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
fourthline.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 220 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 02 | 0 | 0.0 | 267 ms | 0 |
| Tue 04 | 0 | 0.0 | 350 ms | 0 |
| Tue 06 | 0 | 0.0 | 160 ms | 0 |
| Tue 08 | 0 | 0.0 | 64 ms | 0 |
| Tue 10 | 0 | 0.0 | 270 ms | 0 |
| Tue 13 | 0 | 0.0 | 175 ms | 0 |
| Tue 15 | 0 | 0.0 | 301 ms | 0 |
| Tue 17 | 0 | 0.0 | 106 ms | 0 |
| Tue 19 | 0 | 0.0 | 301 ms | 0 |
| Tue 22 | 0 | 0.0 | 226 ms | 0 |
| Wed 00 | 0 | 0.0 | 295 ms | 0 |
| Wed 02 | 0 | 0.0 | 159 ms | 0 |
| Wed 04 | 0 | 0.0 | 281 ms | 0 |
| Wed 06 | 0 | 0.0 | 331 ms | 0 |
| Wed 09 | 0 | 0.0 | 285 ms | 0 |
| Wed 11 | 0 | 0.0 | 365 ms | 0 |
| Wed 13 | 0 | 0.0 | 279 ms | 0 |
| Wed 15 | 0 | 0.0 | 240 ms | 0 |
| Wed 17 | 0 | 0.0 | 376 ms | 0 |
| Wed 20 | 0 | 0.0 | 298 ms | 0 |
| Wed 22 | 0 | 0.0 | 1441 ms | 0 |
| Thu 00 | 0 | 0.0 | 181 ms | 0 |
| Thu 02 | 0 | 0.0 | 253 ms | 0 |
| Thu 04 | 0 | 0.0 | 289 ms | 0 |
| Thu 06 | 0 | 0.0 | 339 ms | 0 |
| Thu 08 | 0 | 0.0 | 235 ms | 0 |
| Thu 10 | 0 | 0.0 | 216 ms | 0 |
| Thu 12 | 0 | 0.0 | 267 ms | 0 |
| Thu 14 | 0 | 0.0 | 332 ms | 0 |
| Thu 16 | 0 | 0.0 | 276 ms | 0 |
| Thu 19 | 0 | 0.0 | 205 ms | 0 |
| Thu 21 | 0 | 0.0 | 302 ms | 0 |
| Thu 23 | 0 | 0.0 | 168 ms | 0 |
| Fri 01 | 0 | 0.0 | 210 ms | 0 |
| Fri 03 | 0 | 0.0 | 160 ms | 0 |
| Fri 05 | 0 | 0.0 | 231 ms | 0 |
| Fri 07 | 0 | 0.0 | 157 ms | 0 |
| Fri 09 | 0 | 0.0 | 300 ms | 0 |
| Fri 10 | 0 | 0.0 | 290 ms | 0 |
| Fri 12 | 0 | 0.0 | 160 ms | 0 |
| Fri 14 | 0 | 0.0 | 160 ms | 0 |
| Fri 16 | 0 | 0.0 | 287 ms | 0 |
| Fri 18 | 0 | 0.0 | 156 ms | 0 |
| Fri 20 | 0 | 0.0 | 196 ms | 0 |
| Fri 22 | 0 | 0.0 | 171 ms | 0 |
| Fri 23 | 0 | 0.0 | 274 ms | 0 |
| Sat 00 | 0 | 0.0 | 233 ms | 0 |
| Sat 02 | 0 | 0.0 | 220 ms | 0 |
100% 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 8 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Fourthline Service yet. Outages of 10 minutes or more get their own page here.
One report per service every 10 minutes from this network. No account.
Get an email when Fourthline Service goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Fourthline Service alerts to Slack, Discord or a webhook — free.
We track Fourthline Service (fourthline.com) as part of the Cloud & developer group. Fourthline solves mission-critical identity challenges for banks, fintechs, & non-financial businesses with a single API integration.
Fourthline Service publishes an official status page at status.fourthline.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: 100% over 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 224 ms average, 156–333 ms range across 14 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Fourthline Service incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
224 ms on average over the last 24 hours (156–333 ms).
Yes, at https://status.fourthline.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 Fourthline Service here at once, the problem is on Fourthline Service'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 Fourthline Service. 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.