bgpreport

Network · data from 2026-11-12

AS263960 AS263960 - speed telecom

Registry name: AS263960 - speed telecom, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS263960, 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:2864:8000::/33 No ROA Nonecovered by 2804:2864::/32 631 99% 67
138.255.85.0/24 No ROA Other IRR onlyRADB 667 99% 67
138.255.86.0/24 No ROA Other IRR onlyRADB 667 99% 67
138.255.84.0/22 No ROA Other IRR onlyRADB 665 99% 67
2804:2864::/32 No ROA Other IRR onlyRADB 631 99% 67

AS-SET

AS263960 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 14 are in fix.csv.

  • ROA: none5
  • Route object: none1
  • Route object: RIR4
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none2804:2864:8000::/33No ROA covers it. Add a ROA for AS263960, maxLength 33.631 of 636
Route object: none2804:2864:8000::/33No route object for it. A route object for 2804:2864::/32 with origin AS263960 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263960 in the RIR database for the space.631 of 636
ROA: none138.255.85.0/24No ROA covers it. Add a ROA for AS263960, maxLength 24.667 of 673
Route object: RIR138.255.85.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
ROA: none138.255.86.0/24No ROA covers it. Add a ROA for AS263960, maxLength 24.667 of 673
Route object: RIR138.255.86.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
ROA: none138.255.84.0/22No ROA covers it. Add a ROA for AS263960, maxLength 22.665 of 673
Route object: RIR138.255.84.0/22Route object only in RADB. Add it in the RIR database for the space.665 of 673
ROA: none2804:2864::/32No ROA covers it. Add a ROA for AS263960, maxLength 32.631 of 636
Route object: RIR2804:2864::/32Route object only in RADB. Add it in the RIR database for the space.631 of 636

Route objects not announced

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

138.255.84.0/23RADBNo ROA
138.255.84.0/24RADBNo ROA
138.255.86.0/23RADBNo ROA
138.255.87.0/24RADBNo 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.