User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Cloud & developer
flizpay.de · Cloud & developer
Is FLIZpay down?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Is it just me?
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Your browser → flizpay.de—
Your browser → us—
Our checksReaching it
Official · ReportsAll clear · Near baseline
DNS (1.1.1.1 · Google)—
Your provider—
Connection—
Upstream—
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.
Live outage map
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.
What's broken
Recent reports
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.
Our checks
Reaching it
Last checked 19 min ago. Last stored result reached it in 594 ms.
Official status
All clear
No active incidents in the official feed Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 10:30 | 0 | 0.0 | 549 ms | 0 |
| 11:00 | 0 | 0.0 | 552 ms | 0 |
| 12:30 | 0 | 0.0 | 657 ms | 0 |
| 14:30 | 0 | 0.0 | 548 ms | 0 |
| 16:30 | 0 | 0.0 | 600 ms | 0 |
| 18:15 | 0 | 0.0 | 567 ms | 0 |
| 20:15 | 0 | 0.0 | 520 ms | 0 |
| 22:00 | 0 | 0.0 | 536 ms | 0 |
| 00:00 | 0 | 0.0 | 588 ms | 0 |
| 02:00 | 0 | 0.0 | 496 ms | 0 |
| 04:00 | 0 | 0.0 | 541 ms | 0 |
| 05:30 | 0 | 0.0 | 553 ms | 0 |
| 05:45 | 0 | 0.0 | 603 ms | 0 |
| 06:15 | 0 | 0.0 | 540 ms | 0 |
| 08:15 | 0 | 0.0 | 594 ms | 0 |
| 08:30 | 0 | 0.0 | 530 ms | 0 |
Reliability
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 7 days of data so far, so the 90-day numbers fill in over time.
Embed this status: free live FLIZpay badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · badge docs · JSON · MCP server
Past outages
No outages on record for FLIZpay yet. Outages of 10 minutes or more get their own page here.
Having trouble with FLIZpay?
One report per service every 10 minutes from this network. No account.
Follow FLIZpay
Get an email when FLIZpay goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send FLIZpay alerts to Slack, Discord or a webhook — free.
About FLIZpay
We track FLIZpay (flizpay.de) as part of the Cloud & developer group. Die Zahlungsmethode aus Deutschland: Bezahle direkt von deinem Bankkonto und spare bei teilnehmenden Shops. Kostenlos für dich.
FLIZpay publishes an official status page at status.flizpay.de; 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 7 days of checks. No public incidents logged since monitoring began 7 days ago.
Response time over the last 24 hours: 559 ms average, 496–657 ms range across 18 successful checks.
Questions
Is FLIZpay down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was FLIZpay last down?
We have not recorded a public FLIZpay incident since monitoring began 7 days ago.
What is FLIZpay's uptime?
From our own checks: 100% over 7 days of checks.
How fast does FLIZpay respond?
559 ms on average over the last 24 hours (496–657 ms).
Does FLIZpay have an official status page?
Yes, at https://status.flizpay.de.
FLIZpay not working for me but the status is fine. What now?
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 FLIZpay here at once, the problem is on FLIZpay'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 FLIZpay. 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.