🌐 PeeringDB Scraper

🚀 Export the global Internet peering registry in seconds. Pull networks (ASNs), Internet Exchanges (IXes), and Facilities (FACs) with ASN, peering policy, traffic class, prefix counts, contact info, and geo data. No API key, no signup.

🕒 Last updated: 2026-05-13 · 📊 25+ fields per record · 🌐 50,000+ networks · 🛰️ 1,000+ IXes · 🏢 5,000+ facilities · 🌍 240+ countries

The PeeringDB Scraper queries the PeeringDB public REST API and returns clean structured records for the three core entity types in the Internet routing ecosystem: Networks (net), Internet Exchanges (ix), and Facilities (fac). Each entity carries up to 25+ fields, including the canonical ID, name and aliases, ASN (for networks), IPv4 and IPv6 prefix counts, traffic class, IPv6 support, peering policy and contracts, location (city, country, continent), media (Ethernet, ATM), site-level counts (net_count, ix_count, fac_count), and contact information (tech, sales, policy emails and phones).

PeeringDB is the open, community-maintained directory used by network engineers worldwide to coordinate peering, plan interconnects, and discover ISPs, content networks, and colocation facilities. This Actor mirrors the same API used by the official PeeringDB web UI, with server-side filtering by country and name substring, and automatic pagination across thousands of records.

🎯 Target Audience	💡 Primary Use Cases
Network engineers, peering coordinators, ISPs, CDN operators, hosting and cloud providers, IXPs, OSINT investigators, journalists	Peering target discovery, ASN lookups, IX participant lists, facility selection, network research, OSINT enrichment, supply-chain mapping

---

📋 What the PeeringDB Scraper does

Three entity modes plus filters in a single run:

• 🌐 Networks (net). Every ASN registered in PeeringDB with peering policy, traffic class, prefix counts, IRR set, and contact info.
• 🛰️ Internet Exchanges (ix). Every IX with city, country, media (Ethernet, ATM), unicast/multicast/IPv6 support, participant count, and service tier.
• 🏢 Facilities (fac). Every colocation facility with operator, address, lat/lon, CLLI, NPA-NXX, voltage services, and counts of networks, IXes, and carriers on site.
• 🌍 Country and name filters. Restrict to one ISO country code (US, DE, NL, JP) and / or a name substring.

Each record includes a deep link back to the PeeringDB profile and the underlying create/update timestamps, so you always know how fresh the upstream entry is.

💡 Why it matters: PeeringDB is the source of truth for inter-network routing relationships. Network engineers use it to find peering partners, ops teams use it to map upstream and downstream dependencies, and OSINT analysts use it to trace ASN ownership and infrastructure footprints. This Actor turns the live registry into a queryable, exportable dataset.

---

🎬 Full Demo

🚧 Coming soon: a 3-minute walkthrough from signup to a downloaded PeeringDB dataset.

---

⚙️ Input

Input	Type	Default	Behavior
maxItems	integer	10	Records to return. Free plan caps at 10, paid plan at 1,000,000.
entity	string	"net"	One of net (Networks), ix (Internet Exchanges), fac (Facilities).
country	string	""	ISO 3166-1 alpha-2 country code. Applies to ix and fac. Empty = worldwide.
name	string	""	Case-insensitive substring filter on the name field. Empty = no filter.

Example: 100 largest content networks worldwide.

{
    "maxItems": 100,
    "entity": "net",
    "name": ""
}

Example: every Internet Exchange in Germany.

{
    "maxItems": 200,
    "entity": "ix",
    "country": "DE"
}

⚠️ Good to Know: the PeeringDB API uses 250-record pages. This Actor handles pagination automatically and respects 429 and 503 backoff. Country filtering applies natively for ix and fac but not for net, since network ASNs are global by definition (use the info_scope field to filter network reach downstream).

---

📊 Output

Each record contains the union of fields relevant to its entity type. Null and empty fields are dropped, so a Facility row carries different keys than a Network row. Download the dataset as CSV, Excel, JSON, or XML.

🧾 Schema (Networks)

Field	Type	Example
🆔 id	number	2
🟢 entity	string	"net"
🏢 name	string	"Akamai Technologies"
🧾 aka	string | null	"Formerly known as nLayer Communications"
🔢 asn	number	20940
🔗 website	string | null	"https://www.akamai.com/"
🪪 irr_as_set	string | null	"AS-AKAMAI"
🏷️ info_type	string | null	"Content"
🏷️ info_types	string[] | null	["Content"]
4️⃣ info_prefixes4	number | null	12000
6️⃣ info_prefixes6	number | null	5000
📊 info_traffic	string | null	"100+Tbps"
⚖️ info_ratio	string | null	"Heavy Outbound"
🌍 info_scope	string | null	"Global"
📡 info_unicast	boolean	true
📺 info_multicast	boolean	false
6️⃣ info_ipv6	boolean	true
📜 policy_general	string	"Open"
📍 policy_locations	string	"Not Required"
⚖️ policy_ratio	boolean	false
📄 policy_contracts	string	"Not Required"
🔗 url	string	"https://www.peeringdb.com/net/2"
🟢 status	string	"ok"
🗓️ created	ISO 8601	"2004-07-28T00:00:00Z"
🗓️ updated	ISO 8601	"2026-04-17T02:41:50Z"
🕒 scrapedAt	ISO 8601	"2026-05-13T22:25:00.795Z"

For ix records you also get city, country, region_continent, media, proto_unicast/multicast/ipv6, tech_email/phone, policy_email/phone, sales_email/phone, net_count, fac_count, and service_level. For fac records you get org_id, org_name, clli, npanxx, address1/2, zipcode, latitude, longitude, plus the same operator and tech contact fields.

📦 Sample records

---

✨ Why choose this Actor

	Capability
🌐	Three entity modes in one Actor. Networks, Internet Exchanges, and Facilities, with consistent schema patterns.
🔢	ASN and ISP enrichment. Peering policy, IRR set, prefix counts, traffic class, and IPv6 readiness in one record.
🛰️	IX participant intelligence. Member counts, facility ties, supported protocols, and contact info per exchange.
🏢	Facility detail. CLLI, NPA-NXX, lat/lon, address, and on-site network and carrier counts.
🌍	Country + name filters. Native PeeringDB filters applied server-side.
📄	Auto-paginated. Handles 250-record pages and 429/503 backoff under the hood.
🚫	No authentication. Anonymous PeeringDB read endpoints. No API key, no login.
🔁	Always fresh. Every run pulls the latest registry state.

📊 PeeringDB is the operational backbone reference for the inter-network routing community.

---

📈 How it compares to alternatives

Approach	Cost	Coverage	Refresh	Filters	Setup
⭐ PeeringDB Scraper (this Actor)	$5 free credit, then pay-per-use	Networks + IXes + Facilities	Live per run	entity, country, name	⚡ 2 min
Raw PeeringDB REST API	Free	Same, but you maintain pagination + filters	On-demand	Build your own	🛠️ Days
RIR whois data	Free	ASN-level only, sparse	RIR cycles	None	🐢 Brittle
Manual page scraping	Free	Fragile	Variable	None	🐢 Brittle

Pick this Actor when you want a ready-to-use, structured PeeringDB dataset with zero pagination or rate-limit handling.

---

🚀 How to use

1. 📝 Sign up. Create a free account with $5 credit (takes 2 minutes).
2. 🌐 Open the Actor. Go to the PeeringDB Scraper page on the Apify Store.
3. 🎯 Set input. Pick an entity (net, ix, or fac), an optional country, a name substring, and maxItems.
4. 🚀 Run it. Click Start and let the Actor pull live records from PeeringDB.
5. 📥 Download. Grab your results from the Dataset tab as CSV, Excel, JSON, or XML.

⏱️ Total time from signup to a downloaded dataset: 3-5 minutes. No coding required.

---

💼 Business use cases

🌐 Network Engineering Peering target discovery by traffic class and policy IX selection by country, participant count, and media Facility shortlists by city and on-site network count ASN-level due diligence before BGP peering sessions	🏢 Sales & Business Development Lead lists of ISPs, CDNs, and hosting providers Targeted outreach to network operators in specific cities Account research on Tier-1 carriers and content networks Channel mapping for telecom and colocation partners
🕵️ OSINT & Investigations ASN ownership and operator history Infrastructure footprint mapping by org Cross-reference for routing-leak investigations Journalism on undersea cable and IX dependencies	📊 Research & Policy IPv6 adoption studies across regions Peering-ecosystem health metrics Internet topology and concentration analysis Reproducible datasets for academic papers

---

🔌 Automating PeeringDB Scraper

Control the scraper programmatically for scheduled runs and pipeline integrations:

• 🟢 Node.js. Install the apify-client NPM package.
• 🐍 Python. Use the apify-client PyPI package.
• 📚 See the Apify API documentation for full details.

The Apify Schedules feature lets you trigger this Actor on any cron interval. Daily pulls keep peering-target lists fresh, weekly pulls capture changes in IX membership and facility counts.

---

🌟 Beyond business use cases

PeeringDB data fuels more than commercial workflows.

🎓 Research and academia Internet topology analyses for academic papers Geospatial mapping of colocation hubs IPv6 readiness studies by region or operator Reproducible coursework on inter-domain routing	🎨 Personal and creative Hobbyist BGP and ASN dashboards Side projects mapping ISPs in a region Visualizations of peering ecosystems Content pieces about how the Internet connects
🤝 Non-profit and civic Civic infrastructure maps for community networks Journalism on routing transparency and outages Open-data feeds for digital-rights orgs Reference data for community ISPs (CommunityIX)	🧪 Experimentation Train ML classifiers on operator type and traffic class Prototype agent pipelines that resolve ASN to org Test routing-policy analyzers with real records Validate hypotheses on IX vs facility growth

---

🤖 Ask an AI assistant about this scraper

Open a ready-to-send prompt about this ParseForge actor in the AI of your choice:

• 💬 ChatGPT
• 🧠 Claude
• 🔍 Perplexity
• 🅒 Copilot

---

❓ Frequently Asked Questions

🧩 How does it work?

The Actor calls the public PeeringDB REST API (/api/{net|ix|fac}) with your country and name filters, paginates 250 records at a time, retries 429 and 503 responses with exponential backoff, and writes one clean record per entity to the dataset.

🔁 How often is the data refreshed?

Every run pulls live records from PeeringDB. The registry itself is community-maintained and updates continuously as operators add and edit entries, so a freshly triggered run reflects the latest state.

🌐 What are net, ix, and fac?

net is a network (ASN), e.g. an ISP, CDN, or content network. ix is an Internet Exchange, the shared fabric where networks peer. fac is a facility, the physical colocation building where networks and IXes are present. Pick one entity per run.

🔢 Can I look up a specific ASN?

This Actor returns lists. To pull a specific ASN, set entity: "net" and use the name filter (PeeringDB indexes ASNs in names like (AS4436)), or run with no filter and grep the dataset on asn downstream.

🌍 Can I filter networks by country?

PeeringDB does not expose a native country filter on the net endpoint, because networks are global by ASN. Use the info_scope field to filter by reach downstream, or filter ix/fac by country to find networks present in a specific region.

🔐 Do I need an API key?

No. PeeringDB's read API is anonymous for unauthenticated access at standard quotas. No login, no API key required.

⏰ Can I schedule regular runs?

Yes. Use Apify Schedules to trigger this Actor on any cron cadence. Daily pulls keep peering-target lists fresh, weekly pulls capture growth in IX membership.

⚖️ Is this data legal to use?

PeeringDB publishes the registry under a permissive license intended specifically for operational and research use. Review the PeeringDB terms for any redistribution, but raw lookup and analytics use cases are well within scope.

💼 Can I use this data commercially?

Yes. PeeringDB data is broadly used in commercial network operations, peering coordination, and sales workflows. Confirm your downstream license obligations for any redistribution.

💳 Do I need a paid Apify plan to use this Actor?

No. The free Apify plan is enough for testing and small runs (10 records per run). A paid plan lifts that limit and unlocks scheduling, higher concurrency, and larger datasets.

🔁 What happens if a run fails or gets interrupted?

Apify automatically retries transient errors. The Actor also retries 429 and 503 responses internally with exponential backoff. Partial datasets from failed runs are preserved, so you never lose progress.

🛬 What if I need related entities like POCs or netixlan?

This Actor returns the three top-level entities (net, ix, fac). For points-of-contact, netixlan (network-to-IX records), and netfac (network-to-facility records), reach out via the contact form for a companion scraper.

🆘 What if I need help?

Our support team is here to help. Contact us through the Apify platform or use the Tally form linked below.

---

🔌 Integrate with any app

PeeringDB Scraper connects to any cloud service via Apify integrations:

• Make - Automate multi-step workflows
• Zapier - Connect with 5,000+ apps
• Slack - Get run notifications in your channels
• Airbyte - Pipe network data into your warehouse
• GitHub - Trigger runs from commits and releases
• Google Drive - Export datasets straight to Sheets

You can also use webhooks to trigger downstream actions when a run finishes. Push fresh peering targets into your CRM, or alert your team in Slack on new IX listings.

---

🔗 Recommended Actors

• 📡 RIPEstat Scraper - IP, ASN, prefix and routing data from the RIPE NCC
• ✈️ OurAirports Scraper - Global airport reference dataset
• 🤖 Hugging Face Model Scraper - Open-source AI model directory
• 🏢 AWS Marketplace Scraper - Cloud software listings and pricing
• 🔌 Stripe App Marketplace Scraper - Fintech app directory metadata

💡 Pro Tip: browse the complete ParseForge collection for more reference-data scrapers.

---

🆘 Need Help? Open our contact form to request a new scraper, propose a custom data project, or report an issue.

---

⚠️ Disclaimer: this Actor is an independent tool and is not affiliated with, endorsed by, or sponsored by PeeringDB or its operators. All trademarks mentioned are the property of their respective owners. Only publicly available registry data is collected.