# Internet Outage Alerts: Connectivity Drops by Country (`scrapemint/internet-outage-alerts`) Actor

Keyless global internet outage detection. Alerts when a country, region or individual network loses connectivity, with the operator name, how many addresses are affected, how far traffic fell against that network's own history, and how many independent measurement systems corroborate the event.

- **URL**: https://apify.com/scrapemint/internet-outage-alerts.md
- **Developed by:** [Ken M](https://apify.com/scrapemint) (community)
- **Categories:** Developer tools, News
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$4.00 / 1,000 outage rows

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/platform/actors/running/actors-in-store#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Internet Outage Alerts: Connectivity Drops by Country

When a country, a region or a single network loses connectivity, measurement systems watching the internet see traffic fall away from that network's own normal level. This reads those alerts and reports what dropped, by how much, and how many independent systems saw it. No key, no login, no proxy.

### What you get

| Field | Meaning |
| --- | --- |
| `entityType`, `entityCode`, `entityName` | A country, a region, a network, or one network inside one country |
| `organisation` | The operator behind the network |
| `addressesAffected` | How much address space that network holds |
| `currentValue`, `historicalValue`, `dropPercent` | How far traffic fell against its own normal level |
| `reportedBySources`, `sourceCount` | Which independent measurement systems saw it |
| `eventKind`, `level` | Outage or recovery, and how severe |
| `time`, `firstSeen` | When it started |

**Summary mode** ranks countries or networks over a window by an outage score, with the score broken out per measurement system and a count of distinct events.

### Example input

```json
{
  "mode": "alerts",
  "hoursBack": 24
}
```

Only well-corroborated, severe events:

```json
{
  "mode": "alerts",
  "hoursBack": 72,
  "minSources": 2,
  "minDropPercent": 50
}
```

### Three things worth knowing

**Most of the raw feed is recoveries, not outages.** An alert at level `normal` means connectivity came back. In a recent 300 alert sample, 171 were recoveries and 129 were outages, so listing the feed unfiltered reports every restoration as an incident. Events are labelled `outage` or `recovery`, and outages only is the default.

**One outage is reported several times.** Four measurement systems watch independently: routing table visibility, active probing, traffic to unused address space, and traffic to a large provider. Each raises its own alert, so a single event appears up to four times. Reports are grouped here by network and time, and `sourceCount` becomes the most useful signal in the output: an event two or three systems agree on is far more likely to be real than one flagged by a single probe. Raise `minSources` to 2 to filter noise.

**Drops are measured against the network's own history, not an absolute threshold.** That is what makes a small regional operator's outage comparable to a national carrier's, and why `dropPercent` is the number to sort on.

### Coverage and honesty about the source

This is a public research service run by a university, not a commercial feed. Coverage is genuinely global and the data is well regarded, but availability guarantees are weaker than a paid product, and a quiet window legitimately returns very little. A run that finds nothing says the internet was quiet rather than pretending to have failed.

### Pricing

Pay per row, `$0.004`. The first 2 rows of every run are free. Quiet windows, filters that remove everything, and source outages return a free note and are never charged.

### Related actors

- **Internet Infrastructure Data** for who owns and routes the networks named here
- **DNS Records Checker** and **SSL Subdomain Finder** for the layers above
- **Global News Media Monitor** for reporting around a major outage

# Actor input Schema

## `mode` (type: `string`):

alerts = one row per outage event with the networks affected. summary = one row per country or network with an outage score for the whole window.

## `hoursBack` (type: `integer`):

How far back to search. A quiet day may return very little, which is the correct answer rather than a failure.

## `entityType` (type: `string`):

country and region are national and subnational outages. asn is a single network operator. geoasn is one operator within one country.

## `country` (type: `array`):

Two letter codes such as NG, IR, SD. Empty watches the whole world.

## `onlyOutages` (type: `boolean`):

On by default. The raw feed mixes recoveries in with outages, and recoveries are the majority. Turn this off to see connectivity returning too.

## `minDropPercent` (type: `integer`):

Keep only events where traffic fell at least this far below the network's own normal level. 0 keeps everything.

## `minSources` (type: `integer`):

How many independent measurement systems must have seen the event. Raising this to 2 is the simplest way to filter out measurement noise.

## `groupEvents` (type: `boolean`):

On by default. Each measurement system reports separately, so without grouping one outage appears as several rows.

## `maxResults` (type: `integer`):

Cap on rows returned. Controls total cost.

## Actor input object example

```json
{
  "mode": "alerts",
  "hoursBack": 24,
  "entityType": "all",
  "country": [],
  "onlyOutages": true,
  "minDropPercent": 0,
  "minSources": 1,
  "groupEvents": true,
  "maxResults": 150
}
```

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "hoursBack": 24,
    "onlyOutages": true,
    "groupEvents": true
};

// Run the Actor and wait for it to finish
const run = await client.actor("scrapemint/internet-outage-alerts").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "hoursBack": 24,
    "onlyOutages": True,
    "groupEvents": True,
}

# Run the Actor and wait for it to finish
run = client.actor("scrapemint/internet-outage-alerts").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "hoursBack": 24,
  "onlyOutages": true,
  "groupEvents": true
}' |
apify call scrapemint/internet-outage-alerts --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,scrapemint/internet-outage-alerts"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/av3zJpkost5tNb7G3/builds/68Bgd4w6f1naS70sS/openapi.json