IsDownMonitor
World alerts
Google DriveProblems — No open incidentsZoomProblems — Service Under MaintenanceClaudeProblems — Claude unable to join meetingsCloudflareProblems — Degraded connectivity between Europe and Asia PacificTwilioProblems — SMS Delivery Receipt Delays from a Subset of Twilio Long Codes to Multiple Networks in ChileKrakenProblems — Ink Network Funding DelaysEntel BoliviaProblems · 🇧🇴Internet outage signal in 🇬🇮 Gibraltarsince · IODAInternet outage signal in 🇹🇩 Chadsince · IODAInternet outage signal in 🇸🇨 Seychellessince · IODAInternet outage signal in 🇬🇶 Equatorial Guineasince · IODAInternet outage signal in 🇫🇮 Finlandsince · IODAInternet outage signal in 🇲🇿 Mozambiquesince · IODAInternet outage signal in 🇨🇰 Cook Islandssince · IODAInternet outage signal in 🇷🇸 Serbiasince · IODAInternet outage signal in 🇭🇹 Haitisince · IODAInternet outage signal in 🇨🇩 Congo - Kinshasasince · IODAInternet outage signal in 🇸🇻 El Salvadorsince · IODAInternet outage signal in 🇹🇯 Tajikistansince · IODA396/419 services operational

Is IPS down in Paraguay?

Government · portal.ips.gov.py

WhatsApp X
Unverified
One check failed — not verified

Only one probe failed. We do not declare an outage from a single signal.

Last update: (Nov 19, 2026, 12:51 AM UTC)Since: Nov 19, 2026, 12:40 AM UTC
Uptime 24 h92.23 %
Uptime 7 days92.49 %
Median response329 ms
Slowest 5 %4,621 ms
Checks 24 h2,341

Signals

  • Our check · Santiago, Chile (Oracle Cloud)responds · HTTP 200 · 208 ms
  • Our check · Chile (local network)responds · HTTP 200 · 249 ms
  • Our check · São Paulo, Brazil (AWS)responds · HTTP 200 · 198 ms
  • Our check · Virginia, USA (AWS)responds · HTTP 200 · 2865 ms
  • Our check · Oregon, USA (AWS)responds · HTTP 200 · 3600 ms
  • Our check · Frankfurt, Germany (AWS)responds · HTTP 200 · 2923 ms
  • Our check · Tokyo, Japan (AWS)responds · HTTP 200 · 4093 ms
  • Our check · Sydney, Australia (AWS)not responding · timeout · 2 failures in a row

Response time — last 24 h

Each line is one probe location. Red marks are failed checks.

0 ms5 s10 sSantiago, Chile (Oracle Cloud) · timeoutChile (local network) · timeoutSão Paulo, Brazil (AWS) · timeoutSantiago, Chile (Oracle Cloud) · timeoutsin-aws · timeoutSydney, Australia (AWS) · timeoutSydney, Australia (AWS) · timeoutsin-aws · timeoutSydney, Australia (AWS) · timeoutsin-aws · timeoutSydney, Australia (AWS) · timeoutSydney, Australia (AWS) · timeoutSydney, Australia (AWS) · timeoutSydney, Australia (AWS) · timeoutSydney, Australia (AWS) · timeoutSydney, Australia (AWS) · timeoutSydney, Australia (AWS) · timeoutSydney, Australia (AWS) · timeoutSydney, Australia (AWS) · timeoutSydney, Australia (AWS) · timeoutSydney, Australia (AWS) · timeoutSydney, Australia (AWS) · timeoutSydney, Australia (AWS) · timeoutSydney, Australia (AWS) · timeoutSydney, Australia (AWS) · timeoutSydney, Australia (AWS) · timeoutSydney, Australia (AWS) · timeoutSydney, Australia (AWS) · timeoutSydney, Australia (AWS) · timeoutSydney, Australia (AWS) · timeoutSydney, Australia (AWS) · timeoutSydney, Australia (AWS) · timeoutSydney, Australia (AWS) · timeoutSydney, Australia (AWS) · timeoutSydney, Australia (AWS) · timeoutSydney, Australia (AWS) · timeoutSydney, Australia (AWS) · timeoutSydney, Australia (AWS) · timeoutSydney, Australia (AWS) · timeoutSydney, Australia (AWS) · timeoutSydney, Australia (AWS) · timeoutSydney, Australia (AWS) · timeoutSydney, Australia (AWS) · timeoutSydney, Australia (AWS) · timeoutSydney, Australia (AWS) · timeoutSydney, Australia (AWS) · timeoutSydney, Australia (AWS) · timeoutSydney, Australia (AWS) · timeoutSydney, Australia (AWS) · timeoutSydney, Australia (AWS) · timeoutSydney, Australia (AWS) · timeoutSydney, Australia (AWS) · timeoutSydney, Australia (AWS) · timeoutSydney, Australia (AWS) · timeoutSydney, Australia (AWS) · timeoutSydney, Australia (AWS) · timeoutSydney, Australia (AWS) · timeoutSydney, Australia (AWS) · timeoutSydney, Australia (AWS) · timeoutSydney, Australia (AWS) · timeoutSydney, Australia (AWS) · timeoutSydney, Australia (AWS) · timeoutSydney, Australia (AWS) · timeoutSydney, Australia (AWS) · timeoutSydney, Australia (AWS) · timeoutSydney, Australia (AWS) · timeoutSydney, Australia (AWS) · timeoutSydney, Australia (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutSydney, Australia (AWS) · timeoutSydney, Australia (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutSydney, Australia (AWS) · timeoutTokyo, Japan (AWS) · timeoutSydney, Australia (AWS) · timeoutSydney, Australia (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutSydney, Australia (AWS) · timeoutTokyo, Japan (AWS) · timeoutSydney, Australia (AWS) · timeoutTokyo, Japan (AWS) · timeoutSydney, Australia (AWS) · timeoutTokyo, Japan (AWS) · timeoutSydney, Australia (AWS) · timeoutTokyo, Japan (AWS) · timeoutSydney, Australia (AWS) · timeoutSydney, Australia (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutSydney, Australia (AWS) · timeoutTokyo, Japan (AWS) · timeoutSydney, Australia (AWS) · timeoutSydney, Australia (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutSydney, Australia (AWS) · timeoutTokyo, Japan (AWS) · timeoutSydney, Australia (AWS) · timeoutTokyo, Japan (AWS) · timeoutSydney, Australia (AWS) · timeoutTokyo, Japan (AWS) · timeoutSydney, Australia (AWS) · timeoutSydney, Australia (AWS) · timeoutTokyo, Japan (AWS) · timeoutSydney, Australia (AWS) · timeoutTokyo, Japan (AWS) · timeoutSydney, Australia (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutSydney, Australia (AWS) · timeoutSydney, Australia (AWS) · timeoutTokyo, Japan (AWS) · timeoutSydney, Australia (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutSydney, Australia (AWS) · timeoutSydney, Australia (AWS) · timeoutTokyo, Japan (AWS) · timeoutSydney, Australia (AWS) · timeoutTokyo, Japan (AWS) · timeoutSydney, Australia (AWS) · timeoutTokyo, Japan (AWS) · timeoutSydney, Australia (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutSydney, Australia (AWS) · timeoutSydney, Australia (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutSydney, Australia (AWS) · timeoutSydney, Australia (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutSydney, Australia (AWS) · timeoutSydney, Australia (AWS) · timeoutSydney, Australia (AWS) · timeoutSydney, Australia (AWS) · timeoutSydney, Australia (AWS) · timeoutSydney, Australia (AWS) · timeoutSydney, Australia (AWS) · timeoutSydney, Australia (AWS) · timeoutSydney, Australia (AWS) · timeoutSydney, Australia (AWS) · timeoutSydney, Australia (AWS) · timeoutSydney, Australia (AWS) · timeoutSydney, Australia (AWS) · timeoutSydney, Australia (AWS) · timeoutSydney, Australia (AWS) · timeoutSydney, Australia (AWS) · timeoutSydney, Australia (AWS) · timeoutTokyo, Japan (AWS) · timeoutSydney, Australia (AWS) · timeoutSydney, Australia (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutSydney, Australia (AWS) · timeoutTokyo, Japan (AWS) · timeoutSydney, Australia (AWS) · timeoutTokyo, Japan (AWS) · timeoutSydney, Australia (AWS) · timeoutSydney, Australia (AWS) · timeoutTokyo, Japan (AWS) · timeoutSydney, Australia (AWS) · timeoutTokyo, Japan (AWS) · timeoutSydney, Australia (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutSydney, Australia (AWS) · timeoutSydney, Australia (AWS) · timeoutTokyo, Japan (AWS) · timeoutSydney, Australia (AWS) · timeoutTokyo, Japan (AWS) · timeoutSydney, Australia (AWS) · timeoutSydney, Australia (AWS) · timeoutSydney, Australia (AWS) · timeoutSydney, Australia (AWS) · timeoutSydney, Australia (AWS) · timeoutSydney, Australia (AWS) · timeoutSydney, Australia (AWS) · timeout-24h-18h-12h-6hnow
Santiago, Chile (Oracle Cloud)Chile (local network)São Paulo, Brazil (AWS)Virginia, USA (AWS)Oregon, USA (AWS)Frankfurt, Germany (AWS)Tokyo, Japan (AWS)Sydney, Australia (AWS)Failure

Availability — last 90 days

90 days ago92.49 %today

Days before monitoring started appear empty.

Incident history

  1. ProblemsNov 19, 2026, 12:38 AM UTCOngoing
    • Problems Most of our probes measure response times far above normal.
    • Unverified Only one probe failed. We do not declare an outage from a single signal.
  2. ProblemsNov 18, 2026, 2:26 PM UTCDuration: 52 min
    • Problems Most of our probes measure response times far above normal.
    • Unverified Only one probe failed. We do not declare an outage from a single signal.
    • Operational Confirmed by at least 2 of our 3 probes in 2 consecutive cycles.
  3. ProblemsNov 18, 2026, 8:33 AM UTCDuration: 2 min
    • Problems Most of our probes measure response times far above normal.
    • Operational Confirmed by at least 2 of our 3 probes in 2 consecutive cycles.

Frequently asked questions

Is IPS down right now?

One check failed — not verified (last update: Nov 19, 2026, 12:51 AM UTC). Only one probe failed. We do not declare an outage from a single signal.

How do you know if IPS is down?

We combine our own checks every 3 minutes from 8 locations. We only confirm an outage when the official source reports it or at least 2 probes fail twice in a row.

IPS isn't working for me but shows operational — what now?

Check whether the problem happens on another network (mobile data vs Wi-Fi). Update or reinstall the app and restart your device. If the official status page reports an incident, wait: it is being worked on. If everything shows as operational, the problem may be your account, device or local connection.

Can I show IPS's status on my site?

Yes. Our widgets and status badge are free for editorial use: https://isdownmonitor.com/widgets