bgpreport

Network · data from 2026-11-12

AS61228 BGP NETWORKS

Registry name: BGP-NETWORKS-LLC BGP NETWORKS LLC, US · PeeringDB

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

Announced routes

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

2a0a:6040:cf02::/48 Valid Nonecovered by 2a0a:6040:cf00::/40 635 100% 69
2602:fb0d::/44 Valid Nonecovered by 2602:fb0d::/40 634 100% 70
2602:fb0d:99::/48 Valid Nonecovered by 2602:fb0d::/40 631 99% 69
23.141.88.0/24 Valid RIR databaseARIN 671 100% 68
2602:fb0d:44::/48 Valid RIR databaseARIN 636 100% 69
2a0a:6040:cf01::/48 Valid RIR databaseRADB, RIPE 636 100% 69
2602:fb0d:33::/48 Valid RIR databaseARIN 635 100% 69
2602:fb0d:77::/48 Valid RIR databaseARIN 635 100% 67
2602:fb0d:aa::/48 Valid RIR databaseARIN 634 100% 68
2602:fb0d:bb::/48 Valid RIR databaseARIN 634 100% 68
2602:fb0d:cc::/48 Valid RIR databaseARIN 634 100% 67
2602:fb0d:22::/48 Valid RIR databaseARIN 605 95% 67

AS-SET

AS61228'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 6 are in fix.csv.

  • Route object: none3
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
Route object: none2a0a:6040:cf02::/48No route object for it. A route object for 2a0a:6040:cf00::/40 with origin AS61228 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61228 in the RIR database for the space.635 of 636
Route object: none2602:fb0d::/44No route object for it. A route object for 2602:fb0d::/40 with origin AS61228 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61228 in the RIR database for the space.634 of 636
Route object: none2602:fb0d:99::/48No route object for it. A route object for 2602:fb0d::/40 with origin AS61228 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61228 in the RIR database for the space.631 of 636

Route objects not announced

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

2602:fb0d::/40ARINNo ROA
2602:fb0d:11::/48ARINValid
2a0a:6040:cf00::/40RIPEValid

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.