User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / 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 36 min ago. Last stored result reached it in 1853 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 06 | 0 | 0.0 | 1979 ms | 0 |
| Mon 08 | 0 | 0.0 | 1991 ms | 0 |
| Mon 10 | 0 | 0.0 | 1716 ms | 0 |
| Mon 12 | 0 | 0.0 | 2115 ms | 0 |
| Mon 14 | 0 | 0.0 | 1930 ms | 0 |
| Mon 16 | 0 | 0.0 | 1449 ms | 0 |
| Mon 18 | 0 | 0.0 | 2164 ms | 0 |
| Mon 20 | 0 | 0.0 | 1535 ms | 0 |
| Mon 23 | 0 | 0.0 | 1504 ms | 0 |
| Tue 01 | 0 | 0.0 | 1031 ms | 0 |
| Tue 03 | 0 | 0.0 | 1898 ms | 0 |
| Tue 05 | 0 | 0.0 | 1961 ms | 0 |
| Tue 07 | 0 | 0.0 | 1605 ms | 0 |
| Tue 09 | 0 | 0.0 | 1917 ms | 0 |
| Tue 11 | 0 | 0.0 | 1786 ms | 0 |
| Tue 13 | 0 | 0.0 | 1602 ms | 0 |
| Tue 16 | 0 | 0.0 | 1024 ms | 0 |
| Tue 18 | 0 | 0.0 | 1430 ms | 0 |
| Tue 20 | 0 | 0.0 | 1989 ms | 0 |
| Tue 22 | 0 | 0.0 | 1493 ms | 0 |
| Wed 01 | 0 | 0.0 | 1523 ms | 0 |
| Wed 03 | 0 | 0.0 | 1040 ms | 0 |
| Wed 05 | 0 | 0.0 | 1487 ms | 0 |
| Wed 07 | 0 | 0.0 | 2081 ms | 0 |
| Wed 10 | 0 | 0.0 | 1296 ms | 0 |
| Wed 12 | 0 | 0.0 | 2007 ms | 0 |
| Wed 14 | 0 | 0.0 | 1963 ms | 0 |
| Wed 16 | 0 | 0.0 | 1847 ms | 0 |
| Wed 18 | 0 | 0.0 | 1452 ms | 0 |
| Wed 20 | 0 | 0.0 | 1567 ms | 0 |
| Wed 23 | 0 | 0.0 | 1955 ms | 0 |
| Thu 01 | 0 | 0.0 | 1952 ms | 0 |
| Thu 03 | 0 | 0.0 | 1946 ms | 0 |
| Thu 05 | 0 | 0.0 | 1824 ms | 0 |
| Thu 07 | 0 | 0.0 | 1812 ms | 0 |
| Thu 09 | 0 | 0.0 | 1746 ms | 0 |
| Thu 11 | 0 | 0.0 | 2169 ms | 0 |
| Thu 13 | 0 | 0.0 | 1617 ms | 0 |
| Thu 15 | 0 | 0.0 | 1877 ms | 0 |
| Thu 17 | 0 | 0.0 | 1783 ms | 0 |
| Thu 19 | 0 | 0.0 | 1693 ms | 0 |
| Thu 21 | 0 | 0.0 | 1783 ms | 0 |
| Fri 00 | 0 | 0.0 | 1586 ms | 0 |
| Fri 02 | 0 | 0.0 | 1065 ms | 0 |
| Fri 04 | 0 | 0.0 | 1112 ms | 0 |
| Fri 06 | 0 | 0.0 | 1744 ms | 0 |
| Fri 08 | 0 | 0.0 | 1225 ms | 0 |
| Fri 10 | 0 | 0.0 | 1853 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 FTAPI 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 FTAPI goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send FTAPI alerts to Slack, Discord or a webhook — free.
We track FTAPI (ftapi.com) as part of the Cloud & developer group. Sensible Daten sicher austauschen ✓ DSGVO-, NIS-2- & DORA-konform ✓ Made & hosted in Germany ✓ für Unternehmen & Behörden. → Jetzt mehr erfahren!
FTAPI publishes an official status page at status.ftapi.com; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with 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: 1560 ms average, 466–2169 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 FTAPI incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
1560 ms on average over the last 24 hours (466–2169 ms).
Yes, at https://status.ftapi.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 FTAPI here at once, the problem is on FTAPI'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 FTAPI. 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.