bgpreport

Network · data from 2026-11-12

AS263462 SPEED PLANET TELECOMUNICAÇÕES LTDA - ME

Registry name: AS263462 - SPEED PLANET TELECOMUNICACOES LTDA - EPP, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS263462, 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.

38.159.191.0/24 No ROA Nonecovered by 38.159.188.0/22 671 100% 66
38.159.189.0/24 No ROA Nonecovered by 38.159.188.0/22 670 100% 66
38.159.190.0/24 No ROA Nonecovered by 38.159.188.0/22 670 100% 66
38.159.188.0/24 No ROA Other IRR onlyRADB 670 100% 66
2804:1230:fc00::/38 Valid Nonecovered by 2804:1230::/32 634 100% 67
177.190.184.0/21 Valid Other IRR onlyRADB, TC 670 100% 66
177.190.184.0/23 Valid Other IRR onlyTC 664 99% 67
177.190.186.0/23 Valid Other IRR onlyTC 664 99% 67
177.190.190.0/23 Valid Other IRR onlyTC 664 99% 67
177.190.188.0/23 Valid Other IRR onlyRADB, TC 663 99% 67
2804:1230::/32 Valid Other IRR onlyRADB, TC 633 100% 67
2804:1230::/35 Valid Other IRR onlyRADB, TC 632 99% 67

AS-SET

PeeringDB's irr_as_set for AS263462: AS263462:AS-SPEED-TELECOM-ALL. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS263462 isn't in the set, or no route object for AS263462 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS263462 in itNot covered
AS263462:AS-SPEED-TELECOM-ALL TC 73363 No 12

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.

  • ROA: none4
  • Route object: none4
  • Route object: RIR8
  • AS-SET: own ASN1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none38.159.191.0/24No ROA covers it. Add a ROA for AS263462, maxLength 24.671 of 673
Route object: none38.159.191.0/24No route object for it. A route object for 38.159.188.0/22 with origin AS263462 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263462 in the RIR database for the space.671 of 673
ROA: none38.159.189.0/24No ROA covers it. Add a ROA for AS263462, maxLength 24.670 of 673
Route object: none38.159.189.0/24No route object for it. A route object for 38.159.188.0/22 with origin AS263462 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263462 in the RIR database for the space.670 of 673
ROA: none38.159.190.0/24No ROA covers it. Add a ROA for AS263462, maxLength 24.670 of 673
Route object: none38.159.190.0/24No route object for it. A route object for 38.159.188.0/22 with origin AS263462 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263462 in the RIR database for the space.670 of 673
ROA: none38.159.188.0/24No ROA covers it. Add a ROA for AS263462, maxLength 24.670 of 673
Route object: RIR38.159.188.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: none2804:1230:fc00::/38No route object for it. A route object for 2804:1230::/32 with origin AS263462 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263462 in the RIR database for the space.634 of 636
Route object: RIR177.190.184.0/21Route object only in RADB, TC. Add it in the RIR database for the space.670 of 673
Route object: RIR177.190.184.0/23Route object only in TC. Add it in the RIR database for the space.664 of 673
Route object: RIR177.190.186.0/23Route object only in TC. Add it in the RIR database for the space.664 of 673
Route object: RIR177.190.190.0/23Route object only in TC. Add it in the RIR database for the space.664 of 673
Route object: RIR177.190.188.0/23Route object only in RADB, TC. Add it in the RIR database for the space.663 of 673
Route object: RIR2804:1230::/32Route object only in RADB, TC. Add it in the RIR database for the space.633 of 636
Route object: RIR2804:1230::/35Route object only in RADB, TC. Add it in the RIR database for the space.632 of 636
AS-SET: own ASNAS263462:AS-SPEED-TELECOM-ALLAS263462 isn't in AS263462:AS-SPEED-TELECOM-ALL (TC) once expanded. Add AS263462 to it.

Route objects not announced

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

38.159.188.0/22RADBNo 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.