User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Cloud & developer
projectdiscovery.io · Cloud & developer
Is ProjectDiscovery 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 → projectdiscovery.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 903 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 13 | 0 | 0.0 | 276 ms | 0 |
| Mon 15 | 0 | 0.0 | 319 ms | 0 |
| Mon 17 | 0 | 0.0 | 268 ms | 0 |
| Mon 19 | 0 | 0.0 | 259 ms | 0 |
| Mon 21 | 0 | 0.0 | 328 ms | 0 |
| Mon 23 | 0 | 0.0 | 220 ms | 0 |
| Tue 01 | 0 | 0.0 | 326 ms | 0 |
| Tue 03 | 0 | 0.0 | 557 ms | 0 |
| Tue 06 | 0 | 0.0 | 384 ms | 0 |
| Tue 08 | 0 | 0.0 | 248 ms | 0 |
| Tue 10 | 0 | 0.0 | 357 ms | 0 |
| Tue 12 | 0 | 0.0 | 288 ms | 0 |
| Tue 14 | 0 | 0.0 | 280 ms | 0 |
| Tue 16 | 0 | 0.0 | 439 ms | 0 |
| Tue 19 | 0 | 0.0 | 343 ms | 0 |
| Tue 21 | 0 | 0.0 | 260 ms | 0 |
| Tue 23 | 0 | 0.0 | 436 ms | 0 |
| Wed 01 | 0 | 0.0 | 399 ms | 0 |
| Wed 04 | 0 | 0.0 | 459 ms | 0 |
| Wed 06 | 0 | 0.0 | 343 ms | 0 |
| Wed 08 | 0 | 0.0 | 298 ms | 0 |
| Wed 10 | 0 | 0.0 | 330 ms | 0 |
| Wed 13 | 0 | 0.0 | 357 ms | 0 |
| Wed 15 | 0 | 0.0 | 275 ms | 0 |
| Wed 17 | 0 | 0.0 | 442 ms | 0 |
| Wed 19 | 0 | 0.0 | 371 ms | 0 |
| Wed 21 | 0 | 0.0 | 320 ms | 0 |
| Wed 23 | 0 | 0.0 | 538 ms | 0 |
| Thu 02 | 0 | 0.0 | 440 ms | 0 |
| Thu 04 | 0 | 0.0 | 287 ms | 0 |
| Thu 06 | 0 | 0.0 | 259 ms | 0 |
| Thu 08 | 0 | 0.0 | 322 ms | 0 |
| Thu 10 | 0 | 0.0 | 291 ms | 0 |
| Thu 12 | 0 | 0.0 | 238 ms | 0 |
| Thu 14 | 0 | 0.0 | 285 ms | 0 |
| Thu 16 | 0 | 0.0 | 249 ms | 0 |
| Thu 18 | 0 | 0.0 | 309 ms | 0 |
| Thu 20 | 0 | 0.0 | 229 ms | 0 |
| Thu 22 | 0 | 0.0 | 341 ms | 0 |
| Fri 00 | 0 | 0.0 | 208 ms | 0 |
| Fri 02 | 0 | 0.0 | 334 ms | 0 |
| Fri 04 | 0 | 0.0 | 525 ms | 0 |
| Fri 06 | 0 | 0.0 | 289 ms | 0 |
| Fri 09 | 0 | 0.0 | 263 ms | 0 |
| Fri 11 | 0 | 0.0 | 454 ms | 0 |
| Fri 13 | 0 | 0.0 | 335 ms | 0 |
| Fri 15 | 0 | 0.0 | 283 ms | 0 |
| Fri 17 | 0 | 0.0 | 595 ms | 0 |
Reliability
100%Uptime · 30 days
100%Uptime · 90 days
0 / 0Outages · 30 / 90 days
—Average outage
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.
Embed this status: free live ProjectDiscovery 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 ProjectDiscovery yet. Outages of 10 minutes or more get their own page here.
Having trouble with ProjectDiscovery?
One report per service every 10 minutes from this network. No account.
Follow ProjectDiscovery
Get an email when ProjectDiscovery goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send ProjectDiscovery alerts to Slack, Discord or a webhook — free.
About ProjectDiscovery
We track ProjectDiscovery (projectdiscovery.io) as part of the Cloud & developer group. ProjectDiscovery maps what your company exposes to the internet, proves which findings are exploitable, and carries each one to a fix with the evidence attached.
ProjectDiscovery publishes an official status page at status.projectdiscovery.io; 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: 371 ms average, 208–903 ms range across 12 successful checks.
Questions
Is ProjectDiscovery down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was ProjectDiscovery last down?
We have not recorded a public ProjectDiscovery incident since monitoring began 8 days ago.
What is ProjectDiscovery's uptime?
From our own checks: 100% over 8 days of checks.
How fast does ProjectDiscovery respond?
371 ms on average over the last 24 hours (208–903 ms).
Does ProjectDiscovery have an official status page?
Yes, at https://status.projectdiscovery.io.
ProjectDiscovery 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 ProjectDiscovery here at once, the problem is on ProjectDiscovery'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 ProjectDiscovery. 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.