bgpreport

Network · data from 2026-11-12

AS23523 Voyageur Internet

Registry name: VOYAGEURINTERNET-1 - Voyageur Internet Inc, CA · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS23523, 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.

162.211.208.0/21 No ROA RIR databaseARIN 671 100% 68
199.204.64.0/21 No ROA RIR databaseARIN 671 100% 68
204.16.144.0/21 No ROA RIR databaseARIN, RADB 671 100% 68
208.74.0.0/21 No ROA RIR databaseARIN, RADB 671 100% 68
2607:ce80::/32 No ROA RIR databaseARIN 634 100% 69

AS-SET

PeeringDB's irr_as_set for AS23523: AS-VOYAGEUR. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS23523 isn't in the set, or no route object for AS23523 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS23523 in itNot covered
AS-VOYAGEUR ARIN 218 Yes 0

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 8 are in fix.csv.

  • ROA: none5
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none162.211.208.0/21No ROA covers it. Add a ROA for AS23523, maxLength 21.671 of 673
ROA: none199.204.64.0/21No ROA covers it. Add a ROA for AS23523, maxLength 21.671 of 673
ROA: none204.16.144.0/21No ROA covers it. Add a ROA for AS23523, maxLength 21.671 of 673
ROA: none208.74.0.0/21No ROA covers it. Add a ROA for AS23523, maxLength 21.671 of 673
ROA: none2607:ce80::/32No ROA covers it. Add a ROA for AS23523, maxLength 32.634 of 636

Route objects not announced

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

64.201.190.0/24RADBNo ROA
207.54.104.0/24RADBNo ROA
2001:470:240::/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.