bgpreport

Network · data from 2026-11-12

AS263914 Speed Wi-Fi Telecom

Registry name: AS263914 - speed wifi telecom, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS263914, 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.185.128.0/23 Invalid: maxLength Nonecovered by 138.185.128.0/22 31 5%low visibility 16
138.185.128.0/22 Valid Other IRR onlyRADB, TC 672 100% 67
138.185.128.0/24 Valid Other IRR onlyRADB 672 100% 67
138.185.129.0/24 Valid Other IRR onlyRADB 672 100% 67
138.185.130.0/23 Valid Other IRR onlyRADB 672 100% 67
138.185.130.0/24 Valid Other IRR onlyRADB 672 100% 67
138.185.131.0/24 Valid Other IRR onlyRADB 672 100% 67
2804:27a4::/33 Valid Other IRR onlyRADB 631 99% 67
2804:27a4:8000::/33 Valid Other IRR onlyRADB 631 99% 67

AS-SET

AS263914'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 15 are in fix.csv.

  • ROA: maxLength1
  • Route object: none1
  • Route object: RIR8
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: maxLength138.185.128.0/23ROA 138.185.128.0/22 AS263914 has maxLength 22; the route is a /23. Raise the maxLength, or add a ROA for 138.185.128.0/23.31 of 673
Route object: none138.185.128.0/23No route object for it. A route object for 138.185.128.0/22 with origin AS263914 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263914 in the RIR database for the space.31 of 673
Route object: RIR138.185.128.0/22Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR138.185.128.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR138.185.129.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR138.185.130.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR138.185.130.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR138.185.131.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR2804:27a4::/33Route object only in RADB. Add it in the RIR database for the space.631 of 636
Route object: RIR2804:27a4:8000::/33Route object only in RADB. Add it in the RIR database for the space.631 of 636

Route objects not announced

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

2804:27a4::/32RADB, TCValid
2804:27a4::/34RADBValid
2804:27a4:4000::/34RADBValid
2804:27a4:8000::/34RADBValid
2804:27a4:c000::/34RADBValid

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.