bgpreport

Network · data from 2026-11-12

AS327906 Embarq

Registry name: Embarq Limited - Embarq Limited, KE · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS327906, 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.
2c0f:f008::/32 Valid None 2 0%low visibility 4
169.255.104.0/22 Valid Other IRR onlyRADB, RIPE-NONAUTH 670 100% 68
102.217.144.0/22 Valid RIR databaseAFRINIC, RADB 670 100% 68

AS-SET

AS327906's PeeringDB record names no 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 15 are in fix.csv.

  • Route object: none1
  • Route object: RIR1
  • Route object: not announced13
ChangePrefix or setDetailFull-table peers
Route object: none2c0f:f008::/32No route object for it. Add a route object with origin AS327906 in the RIR database for the space.2 of 636
Route object: RIR169.255.104.0/22Route object only in RADB, RIPE-NONAUTH. Add it in the RIR database for the space.670 of 673

Route objects not announced

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

102.217.144.0/23RADBValid
102.217.144.0/24RADBValid
102.217.145.0/24RADBValid
102.217.146.0/23RADBValid
102.217.146.0/24RADBValid
102.217.147.0/24RADBValid
169.255.104.0/23RADBValid
169.255.104.0/24RADBValid
169.255.105.0/24RADBValid
169.255.106.0/23RADBValid
169.255.106.0/24RADBValid
169.255.107.0/24RADBValid
2001:470:57d::/48ARINValid

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.