bgpreport

Network · data from 2026-11-12

AS266679 Orbinet

Registry name: AS266679 - ORBINET, EC · PeeringDB

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

Announced routes

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

2803:f920::/40 No ROA Nonecovered by 2803:f920::/32 634 100% 67
2803:f920:b00::/40 No ROA Nonecovered by 2803:f920::/32 634 100% 67
2803:f920:200::/40 Valid RIR databaseLACNIC 634 100% 67
2803:f920:400::/40 Valid RIR databaseLACNIC 634 100% 67
2803:f920:500::/40 Valid RIR databaseLACNIC 634 100% 67
2803:f920:600::/40 Valid RIR databaseLACNIC 634 100% 67
2803:f920:700::/40 Valid RIR databaseLACNIC 634 100% 67
2803:f920:800::/40 Valid RIR databaseLACNIC 634 100% 67
2803:f920:a00::/40 Valid RIR databaseLACNIC 634 100% 67
2803:f920:300::/40 Valid RIR databaseLACNIC 3 0%low visibility 3
2803:f920:100::/40 Valid RIR databaseLACNIC 1 0%low visibility 1

AS-SET

AS266679'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 10 are in fix.csv.

  • ROA: none2
  • Route object: none2
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
ROA: none2803:f920::/40No ROA covers it. Add a ROA for AS266679, maxLength 40.634 of 636
Route object: none2803:f920::/40No route object for it. A route object for 2803:f920::/32 with origin AS266679 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266679 in the RIR database for the space.634 of 636
ROA: none2803:f920:b00::/40No ROA covers it. Add a ROA for AS266679, maxLength 40.634 of 636
Route object: none2803:f920:b00::/40No route object for it. A route object for 2803:f920::/32 with origin AS266679 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266679 in the RIR database for the space.634 of 636

Route objects not announced

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

45.228.52.0/22LACNIC, RADBValid
45.228.52.0/24RADBValid
45.228.53.0/24RADBValid
45.228.54.0/24RADBValid
2803:f920::/32RADBNo ROA
2803:f920:900::/40LACNICValid

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.