labs.llc Outage Internet outages, live
Look up

Outage · off IODA at Georgia Tech, read every five minutes

Internet outage events open now,
by country and by network.

The Internet Outage Detection and Analysis project, IODA, at Georgia Tech watches the internet from outside: which blocks of addresses the world’s routers can still find a way to, which still answer a ping, and how much stray traffic still arrives from them. When one of those signals falls well below its own recent history for a country, a region or a network, IODA opens an event. This page reads those events — what IODA has open now, when each began, which signals saw it and how deep the drop was when it was flagged — and the ones IODA has closed lately.

IODA calls them potential outages, and that is all this page claims for them. A drop in a signal is a measurement, not an explanation: IODA does not say why, and nothing here guesses. An open event is IODA’s record that it has seen no return to normal, not a reading of this minute, so every depth is printed with its age. Look any country, region or network up by name or AS number for its last thirty days of events and seven days of the signals themselves, drawn.

See what is open Look a place up

routing, active probing and a network telescope, and Google’s traffic for countries · every time in UTC · every figure is IODA’s, with the moment it was read · no key, no account

Open now

What IODA has flagged and not yet closed.

Each place below has at least one signal that fell under IODA’s threshold and for which IODA has recorded no return to normal. That is IODA’s record, not the signal this minute: each depth is the figure from the moment of the flag, and on a long-open event the signal may be back. So the places flagged in the last 24 hours come first, deepest drop first, and the older ones follow under a line of their own. IODA opens a routing event for a dip of one per cent just as it does for a total loss; two or three signals falling together is stronger evidence than one.

IODA outage events

asking IODA

Show

Asking IODA…

      Not read yet.

      Source: IODA, the Internet Outage Detection and Analysis project at Georgia Tech.

      Closed lately

      What IODA has closed, and how long each ran.

      IODA closes an event when the signal is back within its threshold of the history value, and that history is a moving figure. When a drop lasts, the history sinks to meet it and the event closes with the signal where it fell: at 17:30 UTC on 6 October 2026, 19 of the 188 network events closed in the day before had ended that way, 17 of them fourteen days to the minute after they opened. So each line prints the closing alert’s two figures beside the flag’s, and says so when the signal had not returned. These are the closed events in the same answer as the list above: seven days of them for countries, twenty-four hours for regions and networks, which have far more. One place can appear several times, once for each signal and each dip.

      Closed in the last 7 days: countries

      Show

      Asking IODA…

        The filter above narrows this list too. Times are UTC; “ran” is from the alert that opened the event to the one that closed it; “not back at close” marks an event whose closing value was still under the level it was flagged at (not judged for Google’s traffic, which is measured against a forecast).

        Look a place up

        One country, region or network.

        Type a country’s name or its two letters, a region’s name, or a network’s name or AS number. The answer is IODA’s record of that place alone: whether it has an open event, every event of the last thirty days, and seven days of each signal drawn from zero, with IODA’s events hatched on it and its latest point set beside any flag still open.

        IODA, one place

          Method

          Where every line comes from, and what it cannot tell you.

          The source

          IODA, Internet Outage Detection and Analysis, is run by the Internet Intelligence Lab at the Georgia Institute of Technology’s College of Computing. Its site says it was originally developed at CAIDA, at the University of California San Diego. It describes itself as an operational prototype that monitors the internet in near real time to identify macroscopic outages: ones that significantly affect a whole network, or a large part of a country.

          This page reads IODA’s public HTTP API, version 2, at api.ioda.inetintel.cc.gatech.edu, which needs no key. It does not read it from your browser. A small relay on this site asks IODA and keeps each answer for every reader, so that however many people have this page open, a research project’s server is asked for each list once in five minutes. Your browser asks labs.llc and nothing else. Three kinds of question are asked: outage events (the lists, and one place’s thirty days), names (the look-up), and raw signals (the drawn lines).

          The signals, in plain words

          Routing (BGP)
          Networks tell each other which addresses they can deliver to. Every five minutes IODA counts, from the public route collectors of RouteViews and RIPE RIS, how many of a place’s /24 blocks (256 addresses each) most of the internet can still see a route to. When routes are withdrawn the blocks cannot be reached from outside, whatever is happening inside.
          Active probing
          IODA pings about 4.2 million /24 blocks roughly every ten minutes and counts the blocks it judges to be up. A fall means machines that used to answer have stopped answering.
          Telescope
          The Merit Network Telescope is a block of unused addresses that only listens. Stray traffic reaches it from everywhere all the time, from scans and misconfigured machines. IODA counts the distinct source addresses seen from a place each minute; when a place goes quiet there too, its machines have stopped reaching the internet.
          Google traffic (countries only)
          Google’s Transparency Report publishes, by country, how much traffic reaches Google’s products. It is half-hourly and, by IODA’s glossary, 60 to 90 minutes behind, so it confirms an outage rather than announcing one. IODA revises the newest points of this line as Google’s figures arrive (on 6 October 2026 the newest half-hour first read a quarter of what it read an hour later), so the look-up marks its end as provisional.

          What an event is, and how sure it is

          For each signal IODA compares the newest figure with a history value for the same place: the median of a sliding window of recent values (by its glossary, 24 hours for routing, seven days for active probing and the telescope), or for Google’s traffic a forecast. Under a set fraction of that history it raises an alert and opens an event. The glossary names two fractions for each signal, a warning (routing 99%, active probing 80%, the telescope 25%) and a critical one (50%, 50% and 10%). In IODA’s answers on 6 October 2026 every opening alert, 690 of 690 in the country and network lists, arrived labelled “critical” with the warning fraction as its condition: routing under 0.99 of its history, probing under 0.8, the telescope under 0.25, Google’s traffic under 0.8. So that label is printed in the small line under each signal as IODA’s API label, with the condition, and is not a grade of severity here: the depth is.

          Open does not mean still down, and closed does not mean it came back. An event stays open in IODA’s record until an alert marked normal arrives, and that is all “open” means on this page. The history value moves. Nigeria’s routing event, open for seventeen days on 6 October 2026, had been flagged at 9,760 blocks against 9,875 and stood at 9,951 that afternoon. And when a drop lasts, the history sinks to it and the event closes with the two figures equal: the network AS56707 was flagged at 37 routed blocks against 53 and closed, fourteen days later to the minute, at 37 against 37. So every depth here is dated; the open list puts the places flagged in the last 24 hours first (that line is this page’s, not IODA’s); a closed line prints the closing alert’s figures and says when the signal had not returned to the level it was flagged at (IODA’s condition times the history of the flag); and the look-up sets each signal’s latest point beside a flag still open.

          IODA gives no probability that an event is a real outage. Its own way to gain confidence, in its glossary’s words, is to use several signals: it multiplies the score of each signal that raised an alert into an Overall Score, so that an outage seen by more than one signal weighs more. IODA’s API gives that product for a place over a whole window, closed events included, and it is on IODA’s dashboard; it is not printed here. What is printed are its parts for the events still open: how many independent signals flag the place at once, and each signal’s own score, which IODA calls Alert Area: the percentage of the drop multiplied by the minutes the event has run, so an old shallow dip can outscore a new deep one. The depth is worked out here from the two figures of the opening alert (the value against the history value).

          How fresh it is

          Each list is read from IODA at most once in five minutes for all readers together, over a window that ends on this server’s clock rounded down to five minutes, and this page asks again every five minutes while it is open and in view. IODA itself runs behind the moment: on 6 October 2026 its newest alerts were between half an hour and seventy minutes old when read, and countries are flagged far less often than networks. Every list says when it was read and when its window ended. A name is kept for a day, a drawn signal for ten minutes.

          When IODA is slow, down or rate-limiting, the page says which, in the relay’s own words, and keeps the last list it had, marked with its age, for at most six hours: the relay’s copy, the copy this browser kept, and the one an open tab is holding. After that it shows nothing rather than something stale. A list is called live only while its read is younger than one five-minute round and a retry; past that it is a kept copy with the time of its read. The page never fills a gap with an estimate, and an answer with no events is printed as IODA listing none, not as an all-clear.

          What this page does not know

          • Why. IODA gives no cause, and a fall in a signal has many: a cut cable, a power failure, a storm, maintenance, a routing mistake, an order to switch networks off. This page names none of them.
          • Whether your own connection is affected. IODA sees large outages from outside. One street, one building or one mobile cell is below what it can see, and a network that does not answer pings is invisible to active probing.
          • What the signal is doing this minute. The depth printed with an event is from the alert that opened it, and says how long ago that was. The signal may have fallen further, half recovered or fully recovered since; the look-up draws its last seven days, in half-hour averages.
          • Whether an open event is still an outage. IODA’s record is open until IODA closes it, which can be days after the signal is back or, when the drop lasts, about fourteen days on with the signal still down. IODA searches fourteen days before each window for events still open, so an older one leaves these lists while it is still open. An event that has run for weeks may be a lasting change in a network rather than a fault. IODA does not say which.
          • Anything IODA has not detected. A place with no event here has no event at IODA; that is not proof that all is well there.
          • Borders. Addresses are placed in countries and regions by a commercial geolocation database (IPinfo’s, IODA says), which is sometimes wrong, and the names of places are printed as IODA spells them.
          • IPv6. The blocks counted are IPv4 /24s.

          Licence and attribution

          IODA publishes no licence and no terms-of-use page for its data. Each answer from its API carries a notice instead, which is printed under the lists above as it arrived and read, on 6 October 2026:

          This data is Copyright (c) 2021-2025 Georgia Tech Research Corporation. All Rights Reserved.

          So this page reports IODA’s findings under that notice, names IODA beside them, and links every place to its page on IODA’s own dashboard, which is the authority on it. The relay holds IODA’s latest answer to each question for the minutes or hours given above and hands it on whole and unchanged, so a program that asks the relay’s address directly is given the same answer this page is; nothing is archived or offered as a download. IODA’s signals rest in turn on RouteViews, RIPE RIS, the Merit Network Telescope and Google’s Transparency Report. The project can be reached at ioda-info@cc.gatech.edu.

          Cloudflare Radar’s outage annotations are an optional second source. Radar’s API needs a token, so they appear in a band of their own only when this server has been given one, and the line under the first list always says whether it has. Cloudflare publishes Radar’s data under CC BY-NC 4.0 (attribution, non-commercial), and the band names it.

          What you type, and what is kept

          A name or number typed into the look-up goes to this site’s relay and from there to IODA as a search word, so IODA sees the word and this server’s address, not yours. The relay refuses the pages of other sites, counts each caller’s questions so that nobody can drive IODA hard through it, and keeps IODA’s answers for the times given above. The place you open is written after the # of this page’s address so it can be sent to somebody; your browser keeps the last list it read, so that a reload while IODA is silent still has something true to show, and the kind and order you chose. This is a report of public measurements, not a service to rely on in an emergency. Questions and corrections: labs@labs.llc.