bgpreport

Network · data from 2026-11-12

AS264591 AS264591 - 7 Sul Telecom

Registry name: AS264591 - 7 Sul Telecom, BR · not in PeeringDB

7IPv4 routes 100.0% RPKI valid · 100.0% with a route object
3IPv6 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
0Route objects not announced registered with origin AS264591, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS264591, 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.200.0/22 Valid Other IRR onlyALTDB, RADB, TC 667 99% 67
138.36.200.0/23 Valid Other IRR onlyALTDB, RADB, TC 667 99% 67
138.36.200.0/24 Valid Other IRR onlyALTDB, RADB, TC 667 99% 67
138.36.202.0/23 Valid Other IRR onlyALTDB, RADB, TC 667 99% 67
138.36.202.0/24 Valid Other IRR onlyALTDB, RADB, TC 667 99% 67
138.36.201.0/24 Valid Other IRR onlyALTDB, RADB, TC 665 99% 67
138.36.203.0/24 Valid Other IRR onlyALTDB, RADB, TC 665 99% 67
2804:2218::/33 Valid Other IRR onlyALTDB, TC 635 100% 67
2804:2218:8000::/33 Valid Other IRR onlyALTDB, TC 635 100% 67
2804:2218::/32 Valid Other IRR onlyALTDB, RADB, TC 631 99% 67

AS-SET

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

  • Route object: RIR10
ChangePrefix or setDetailFull-table peers
Route object: RIR138.36.200.0/22Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.667 of 673
Route object: RIR138.36.200.0/23Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.667 of 673
Route object: RIR138.36.200.0/24Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.667 of 673
Route object: RIR138.36.202.0/23Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.667 of 673
Route object: RIR138.36.202.0/24Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.667 of 673
Route object: RIR138.36.201.0/24Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.665 of 673
Route object: RIR138.36.203.0/24Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.665 of 673
Route object: RIR2804:2218::/33Route object only in ALTDB, TC. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:2218:8000::/33Route object only in ALTDB, TC. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:2218::/32Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.631 of 636

Route objects not announced

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