User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Cloud & developer
filigran.io · Cloud & developer
Is Filigran 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 → filigran.io—
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 1 hr ago. Last stored result reached it in 742 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 |
|---|---|---|---|---|
| Mon 23 | 0 | 0.0 | 433 ms | 0 |
| Tue 01 | 0 | 0.0 | 450 ms | 0 |
| Tue 03 | 0 | 0.0 | 504 ms | 0 |
| Tue 05 | 0 | 0.0 | 385 ms | 0 |
| Tue 07 | 0 | 0.0 | 410 ms | 0 |
| Tue 09 | 0 | 0.0 | 379 ms | 0 |
| Tue 11 | 0 | 0.0 | 780 ms | 0 |
| Tue 14 | 0 | 0.0 | 237 ms | 0 |
| Tue 16 | 0 | 0.0 | 404 ms | 0 |
| Tue 18 | 0 | 0.0 | 410 ms | 0 |
| Tue 20 | 0 | 0.0 | 586 ms | 0 |
| Tue 23 | 0 | 0.0 | 383 ms | 0 |
| Wed 01 | 0 | 0.0 | 397 ms | 0 |
| Wed 03 | 0 | 0.0 | 591 ms | 0 |
| Wed 05 | 0 | 0.0 | 807 ms | 0 |
| Wed 07 | 0 | 0.0 | 298 ms | 0 |
| Wed 08 | 0 | 0.0 | 67 ms | 0 |
| Wed 10 | 0 | 0.0 | 234 ms | 0 |
| Wed 12 | 0 | 0.0 | 564 ms | 0 |
| Wed 14 | 0 | 0.0 | 411 ms | 0 |
| Wed 16 | 0 | 0.0 | 392 ms | 0 |
| Wed 18 | 0 | 0.0 | 473 ms | 0 |
| Wed 21 | 0 | 0.0 | 470 ms | 0 |
| Wed 23 | 0 | 0.0 | 595 ms | 0 |
| Thu 01 | 0 | 0.0 | 508 ms | 0 |
| Thu 03 | 0 | 0.0 | 377 ms | 0 |
| Thu 05 | 0 | 0.0 | 456 ms | 0 |
| Thu 07 | 0 | 0.0 | 600 ms | 0 |
| Thu 09 | 0 | 0.0 | 449 ms | 0 |
| Thu 11 | 0 | 0.0 | 395 ms | 0 |
| Thu 13 | 0 | 0.0 | 633 ms | 0 |
| Thu 15 | 0 | 0.0 | 580 ms | 0 |
| Thu 17 | 0 | 0.0 | 414 ms | 0 |
| Thu 19 | 0 | 0.0 | 520 ms | 0 |
| Thu 21 | 0 | 0.0 | 418 ms | 0 |
| Fri 00 | 0 | 0.0 | 397 ms | 0 |
| Fri 02 | 0 | 0.0 | 380 ms | 0 |
| Fri 04 | 0 | 0.0 | 233 ms | 0 |
| Fri 06 | 0 | 0.0 | 577 ms | 0 |
| Fri 08 | 0 | 0.0 | 492 ms | 0 |
| Fri 10 | 0 | 0.0 | 544 ms | 0 |
| Fri 12 | 0 | 0.0 | 588 ms | 0 |
| Fri 14 | 0 | 0.0 | 528 ms | 0 |
| Fri 16 | 0 | 0.0 | 440 ms | 0 |
| Fri 18 | 0 | 0.0 | 529 ms | 0 |
| Fri 20 | 0 | 0.0 | 614 ms | 0 |
| Fri 21 | 0 | 0.0 | 427 ms | 0 |
| Fri 23 | 0 | 0.0 | 742 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 Filigran 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 Filigran yet. Outages of 10 minutes or more get their own page here.
Having trouble with Filigran?
One report per service every 10 minutes from this network. No account.
Follow Filigran
Get an email when Filigran goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Filigran alerts to Slack, Discord or a webhook — free.
About Filigran
Filigran, at filigran.io, is one of the Cloud & developer services we monitor. Embrace a proactive approach with end-to-end cyber threat management, from anticipation to response.
Filigran publishes an official status page at status.filigran.io; 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 7 days of checks. No public incidents logged since monitoring began 7 days ago.
Response time over the last 24 hours: 488 ms average, 68–742 ms range across 16 successful checks.
Questions
Is Filigran down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was Filigran last down?
We have not recorded a public Filigran incident since monitoring began 7 days ago.
What is Filigran's uptime?
From our own checks: 100% over 7 days of checks.
How fast does Filigran respond?
488 ms on average over the last 24 hours (68–742 ms).
Does Filigran have an official status page?
Yes, at https://status.filigran.io.
Filigran 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 Filigran here at once, the problem is on Filigran'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 Filigran. 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.