bgpreport

Network · data from 2026-11-12

AS263957 SEU LUGAR TELECOM

Registry name: AS263957 - SEU LUGAR TELECOM, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS263957, 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.255.8.0/24 No ROA Other IRR onlyRADB, TC 672 100% 67
138.255.9.0/24 No ROA Other IRR onlyRADB, TC 672 100% 67
138.255.11.0/24 No ROA Other IRR onlyRADB, TC 671 100% 66
2804:2858::/32 No ROA Other IRR onlyRADB, TC 635 100% 67

AS-SET

AS263957'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 46 are in fix.csv.

  • ROA: none4
  • Route object: RIR4
  • Route object: not announced38
ChangePrefix or setDetailFull-table peers
ROA: none138.255.8.0/24No ROA covers it. Add a ROA for AS263957, maxLength 24.672 of 673
Route object: RIR138.255.8.0/24Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
ROA: none138.255.9.0/24No ROA covers it. Add a ROA for AS263957, maxLength 24.672 of 673
Route object: RIR138.255.9.0/24Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
ROA: none138.255.11.0/24No ROA covers it. Add a ROA for AS263957, maxLength 24.671 of 673
Route object: RIR138.255.11.0/24Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
ROA: none2804:2858::/32No ROA covers it. Add a ROA for AS263957, maxLength 32.635 of 636
Route object: RIR2804:2858::/32Route object only in RADB, TC. Add it in the RIR database for the space.635 of 636

Route objects not announced

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

138.255.8.0/22RADB, TCNo ROA
138.255.8.0/23RADB, TCNo ROA
138.255.10.0/23RADB, TCNo ROA
138.255.10.0/24RADB, TCNo ROA
2804:2858::/33RADB, TCNo ROA
2804:2858::/34RADBNo ROA
2804:2858::/35RADBNo ROA
2804:2858::/36RADBNo ROA
2804:2858:1000::/36RADBNo ROA
2804:2858:2000::/35RADBNo ROA
2804:2858:2000::/36RADBNo ROA
2804:2858:3000::/36RADBNo ROA
2804:2858:4000::/34RADBNo ROA
2804:2858:4000::/35RADBNo ROA
2804:2858:4000::/36RADBNo ROA
2804:2858:5000::/36RADBNo ROA
2804:2858:6000::/35RADBNo ROA
2804:2858:6000::/36RADBNo ROA
2804:2858:7000::/36RADBNo ROA
2804:2858:8000::/33RADB, TCNo ROA
2804:2858:8000::/34RADBNo ROA
2804:2858:8000::/35RADBNo ROA
2804:2858:8000::/36RADBNo ROA
2804:2858:8000::/44ALTDB, RADBNo ROA
2804:2858:9000::/36RADBNo ROA
2804:2858:a000::/35RADBNo ROA
2804:2858:a000::/36RADBNo ROA
2804:2858:b000::/36RADBNo ROA
2804:2858:c000::/34RADBNo ROA
2804:2858:c000::/35RADBNo ROA
2804:2858:c000::/36RADBNo ROA
2804:2858:d000::/36RADBNo ROA
2804:2858:e000::/35RADBNo ROA
2804:2858:e000::/36RADBNo ROA
2804:2858:f000::/36RADBNo ROA
2804:2858:ff00::/40RADBNo ROA
2804:2858:ff20::/48RADBNo ROA
2804:2858:ff30::/44RADBNo ROA

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.