bgpreport

Network · data from 2026-11-12

AS33604 Burlington Telecom

Registry name: BTNETWORK - Burlington Telecom, US · PeeringDB

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

Announced routes

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

38.69.196.0/22 No ROA Other IRR onlyRADB 671 100% 68
65.183.128.0/19 Valid RIR databaseARIN 671 100% 68
69.5.112.0/20 Valid RIR databaseARIN 671 100% 68
162.247.88.0/22 Valid RIR databaseARIN 671 100% 68
204.13.40.0/21 Valid RIR databaseARIN, RADB 671 100% 68
2606:8600::/32 Valid RIR databaseARIN 636 100% 69

AS-SET

PeeringDB's irr_as_set for AS33604: AS33604:AS-ALL. 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 (AS33604 isn't in the set, or no route object for AS33604 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 objectsAS33604 in itNot covered
AS33604:AS-ALL ARIN 6212 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 2 are in fix.csv.

  • ROA: none1
  • Route object: RIR1
ChangePrefix or setDetailFull-table peers
ROA: none38.69.196.0/22No ROA covers it. Add a ROA for AS33604, maxLength 22.671 of 673
Route object: RIR38.69.196.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673

Route objects not announced

Every route object with origin AS33604 is announced.

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.