BGP Routing Tables and Prefix Announcements

This dataset provides detailed BGP routing table snapshots, including advertised IP prefixes, AS paths, route origins, BGP communities, and route selection metrics such as local preference and MED. It enables analysis of global internet routing dynamics, prefix aggregation, and network policy propagation, making it valuable for network operators, researchers, and security analysts.

  • last updated 1 Nov 2025
  • by GoMask
The brief that made it

Analyzing global internet routing and prefix propagation

Sample rows

preview · 8 of 700 rows · all 11 columns
prefixstringroute_origin_typestringlocal_prefintegeraggregatedbooleancollector_idstringas_pathstringorigin_asintegernext_hopstringmedintegerbgp_communitiesstringtimestampdatetime
8.8.8.0/24EGP120falseCOLL-GLOBAL15169 3356 64512645128.8.8.11064512:100 3356:2002024-06-21T08:15:32Z
10.0.0.0/8IGP80trueCOLL-A1650016500110.0.0.10blank2024-06-13T14:22:05Z
185.25.60.0/22EGP150falseCOLL-EUROPE6939 6450064500185.25.60.15064500:2202024-06-19T12:01:37Z
0.0.0.0/0INCOMPLETE32767trueCOLL-ROOT65535655350.0.0.10blank2024-06-22T01:09:45Z
192.168.100.0/24IGP90falseCOLL-ENTERPRISE65010 6502065020192.168.100.12blank2024-06-16T15:27:12Z
2.2.2.0/23EGP110falseCOLL-ASIA6939 12345 67890678902.2.2.21567890:3002024-06-10T09:53:28Z
224.0.0.0/4INCOMPLETEblanktrueCOLL-MULTICAST6550065500224.0.0.1blankblank2024-06-18T05:44:11Z
172.16.0.0/12IGP0trueCOLL-ENTERPRISE65000 6500165001172.16.0.10blank2024-06-22T13:10:19Z

What the 700 rows show

from the 700-row sample

INCOMPLETE (route origin type) stands out: mean local_pref is 501,093,722, against 22,526,140 for the rest.

  • 51%aggregated = true
  • 100median local_pref
  • 64,538median origin_as
  • 10median med
Mean local_pref by route_origin_type632 rows
0400M800M43.7IGP261 rows41.4MEGP311 rows501.1MINCOMPLETE60 rows
local_pref632 rows, in bands of 250M
031062061200000002001.3B2.3Blocal_pref →

Median 100, from 0 to 2,147,483,647.

collector_id700 rows · top 10 of 23 values
  1. COLL-ENTERPRISE118
  2. COLL-GLOBAL83
  3. COLL-EUROPE83
  4. COLL-A174
  5. COLL-ASIA67
  6. COLL-ISOLATED66
  7. COLL-EXPERIMENTAL31
  8. COLL-MULTICAST30
  9. COLL-LATAM24
  10. COLL-APIPA23
11 columns by typefrom the column list below
  • string 6
  • integer 3
  • datetime 1
  • boolean 1

Columns

11 columns in four groups
blueprint · 11 columns
columntypedescriptionexample
Text 6 columns
prefixstringAdvertised IP prefix in CIDR notation (e.g., 192.0.2.0/24)8.8.8.0/24
as_pathstringSequence of AS numbers traversed to reach the prefix, separated by spaces (e.g., '64512 64513 64514')15169 3356 64512
next_hopstringIP address of the next-hop router for the route8.8.8.1
bgp_communitiesstringSpace-separated list of BGP community values associated with the route (e.g., '64512:100 64513:200')optional64512:100 3356:200
route_origin_typestringType of route origin (e.g., 'IGP', 'EGP', 'INCOMPLETE')IGP · EGP · INCOMPLETE · optionalEGP
collector_idstringIdentifier for the BGP collector or monitoring point where the route was observedCOLL-GLOBAL
Numbers 3 columns
origin_asintegerAutonomous System Number (ASN) that originated the prefix announcement1 or more64512
local_prefintegerLocal preference value used to select preferred routes within an AS0 or more · optional120
medintegerMulti-Exit Discriminator value indicating preferred entry points between ASes0 or more · optional10
Dates and times 1 column
timestampdatetimeDate and time when the prefix announcement was observed2024-06-21T08:15:32Z
True or false 1 column
aggregatedbooleanIndicates whether the prefix is the result of aggregation (true) or a specific announcement (false)false

Use it for

  • aggregated51%354 of 700 rowsmean local pref by ro…43.7IGP41.4MEGP501.1MINCOMP…

    A telecommunications dashboard

    The aggregated rate, local_pref by route_origin_type and a breakdown of collector_id. Excel, Power BI or Tableau.

  • Why do the 60 INCOMPLETE rows have a mean local_pref of 501,093,722?

    A root-cause class exercise

    Hand out the rows and one question. The answer is in the data, not in the brief.

  • A software demo

    Believable prefixes with as_path, origin_as and next_hop to fill a screen in front of a buyer.

Not quite right?

Make it yours.

Same 11 columns, your size and your rules. See 20 rows before you pay.

Preview 20 rows free

1,000 rows: $1.99 · 10,000: $12.99One-time. No subscription. All prices

This dataset700 rows11 columns
Yours1,000 rows11 columns

blueprint · bgp-routing-tables-and-prefix-announcements

Behind this dataset

Same schema. As many rows as you need.

These 700 rows came out of a blueprint — 11 columns with generation rules behind each one. Open it in Data Factory to retune a column, add your own, wire in foreign keys, and run it at the size you actually need.

Rules it was built with
  • Prefix announced: IPv4 CIDR (e.g., 203.0.113.0/24) or IPv6
  • AS number: autonomous system number of originating network
  • AS path: sequence of AS numbers from origin to destination
  • BGP communities: tags for route policy (no-export, prepending, etc.)
  • Route origin: IGP (interior gateway protocol), EGP, incomplete
  • Next-hop: router IP address for forwarding traffic
  • Local preference: route preference within AS (higher is better)
  • MED (Multi-Exit Discriminator): prefer certain paths for inbound traffic
Rows
Open the blueprint in Data Factory

1 credit per row. Preview 20 rows free. Buy rows for the full run.

Exports
CSV, JSON, JSONL, Parquet, SQL, Excel, TSV, XML
Licence
yours to use, including commercially
API slug
bgp-routing-tables-and-prefix-announcements

More in Telecommunications

Browse all
Also in TelecommunicationsTelecom Network Carbon Emission LogsTelecommunications Equipment Failure LogsRoaming CDR and TAP/RAP File ProcessingAll 1,967 datasets

What should your data show?

Preview 20 rows free
No signup. No card.