bgpreport

Network · data from 2026-11-12

AS54040 NBCUNI - NBCUniversal

Registry name: NBCUNI - NBCUniversal, US · not in PeeringDB

2IPv4 routes 50.0% RPKI valid · 0.0% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
1No ROA 2 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
6Route objects not announced registered with origin AS54040, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS54040, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.

216.39.34.0/23 No ROA Other origin only 673 100% 67
50.234.250.0/24 Valid Other origin only 673 100% 67

AS-SET

AS54040 isn't in PeeringDB, where networks name their AS-SET.

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 9 are in fix.csv.

  • ROA: none1
  • Route object: none2
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
ROA: none216.39.34.0/23No ROA covers it. Add a ROA for AS54040, maxLength 23.673 of 673
Route object: none216.39.34.0/23Route objects for it name AS22694. Add a route object with origin AS54040 in the RIR database for the space.673 of 673
Route object: none50.234.250.0/24Route objects for it name AS22694. Add a route object with origin AS54040 in the RIR database for the space.673 of 673

Route objects not announced

Route objects with origin AS54040 whose prefix no peer sees AS54040 announce. Many are kept on purpose (backup routes, space announced only in some places).

50.207.32.0/21RADBValid
50.228.144.0/20RADBValid
173.213.208.0/20RADBNo ROA
204.237.131.0/24RADBNo ROA
2001:668:121::/48RADBValid
2001:668:122::/48RADBValid

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.