bgpreport

Network · data from 2026-11-12

AS266975 EURONET TELECOM

Registry name: AS266975 - EURONET TELECOM, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS266975, 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.
2804:4634:9c41::/48 Invalid: maxLength Nonecovered by 2804:4634::/32 1 0%low visibility 1
45.226.36.0/22 No ROA Other IRR onlyALTDB, RADB, TC 2 0%low visibility 2
45.226.36.0/23 Valid Nonecovered by 45.226.36.0/22 671 100% 66
2804:4634:9c40::/48 Valid Nonecovered by 2804:4634::/32 630 99% 67
45.226.38.0/24 Valid Other IRR onlyRADB 672 100% 67
45.226.39.0/24 Valid Other IRR onlyRADB 669 99% 67
45.226.36.0/24 Valid Other IRR onlyRADB 130 19% 44
45.226.37.0/24 Valid Other IRR onlyRADB 130 19% 45
2804:4634::/32 Valid Other IRR onlyALTDB, RADB, TC 3 0%low visibility 3

AS-SET

AS266975'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 11 are in fix.csv.

  • ROA: maxLength1
  • ROA: none1
  • Route object: none3
  • Route object: RIR6
ChangePrefix or setDetailFull-table peers
ROA: maxLength2804:4634:9c41::/48ROA 2804:4634::/32 AS266975 has maxLength 32; the route is a /48. Raise the maxLength, or add a ROA for 2804:4634:9c41::/48.1 of 636
Route object: none2804:4634:9c41::/48No route object for it. A route object for 2804:4634::/32 with origin AS266975 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266975 in the RIR database for the space.1 of 636
ROA: none45.226.36.0/22No ROA covers it. Add a ROA for AS266975, maxLength 22.2 of 673
Route object: RIR45.226.36.0/22Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.2 of 673
Route object: none45.226.36.0/23No route object for it. A route object for 45.226.36.0/22 with origin AS266975 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266975 in the RIR database for the space.671 of 673
Route object: none2804:4634:9c40::/48No route object for it. A route object for 2804:4634::/32 with origin AS266975 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266975 in the RIR database for the space.630 of 636
Route object: RIR45.226.38.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR45.226.39.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR45.226.36.0/24Route object only in RADB. Add it in the RIR database for the space.130 of 673
Route object: RIR45.226.37.0/24Route object only in RADB. Add it in the RIR database for the space.130 of 673
Route object: RIR2804:4634::/32Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.3 of 636

Route objects not announced

Every route object with origin AS266975 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.