bgpreport

Network · data from 2026-11-12

AS264589 AS264589 - AGRESTE LINK

Registry name: AS264589 - AGRESTE LINK, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS264589, 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.
138.36.240.0/22 Valid Other IRR onlyALTDB, RADB, TC 672 100% 66
138.36.240.0/23 Valid Other IRR onlyTC 672 100% 67
143.202.228.0/23 Valid Other IRR onlyTC 672 100% 66
138.36.242.0/23 Valid Other IRR onlyTC 669 99% 66
143.202.231.0/24 Valid Other IRR onlyTC 669 99% 66
143.202.230.0/24 Valid Other IRR onlyTC 666 99% 67
2804:2210::/32 Valid Other IRR onlyALTDB, RADB, TC 635 100% 69
2804:2210::/48 Valid Other IRR onlyRADB 635 100% 69

AS-SET

AS264589 isn't in PeeringDB, where networks name their 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 18 are in fix.csv.

  • Route object: RIR8
  • Route object: not announced10
ChangePrefix or setDetailFull-table peers
Route object: RIR138.36.240.0/22Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR138.36.240.0/23Route object only in TC. Add it in the RIR database for the space.672 of 673
Route object: RIR143.202.228.0/23Route object only in TC. Add it in the RIR database for the space.672 of 673
Route object: RIR138.36.242.0/23Route object only in TC. Add it in the RIR database for the space.669 of 673
Route object: RIR143.202.231.0/24Route object only in TC. Add it in the RIR database for the space.669 of 673
Route object: RIR143.202.230.0/24Route object only in TC. Add it in the RIR database for the space.666 of 673
Route object: RIR2804:2210::/32Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:2210::/48Route object only in RADB. Add it in the RIR database for the space.635 of 636

Route objects not announced

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

138.36.240.0/24TCValid
138.36.241.0/24TCValid
138.36.242.0/24TCValid
138.36.243.0/24TCValid
143.202.228.0/22ALTDB, RADB, TCNo ROA
143.202.228.0/24TCValid
143.202.229.0/24TCValid
143.202.230.0/23TCNo ROA
2804:2210::/33TCValid
2804:2210:8000::/33TCValid

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.