bgpreport

Network · data from 2026-11-12

AS26104 AS26104 - Telespazio Brasil S.A.

Registry name: AS26104 - Telespazio Brasil S.A., BR · not in PeeringDB

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

Announced routes

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

200.142.160.0/21 No ROA None 670 100% 67
2804:4234::/33 No ROA None 2 0%low visibility 2
2804:4234::/40 No ROA None 2 0%low visibility 2
200.142.169.0/24 No ROA Other IRR onlyRADB 671 100% 67
200.142.170.0/24 No ROA Other IRR onlyRADB 671 100% 67
200.142.172.0/24 No ROA Other IRR onlyRADB 671 100% 67
200.142.173.0/24 No ROA Other IRR onlyRADB 671 100% 67
200.142.174.0/24 No ROA Other IRR onlyRADB 671 100% 67
200.142.175.0/24 No ROA Other IRR onlyRADB 671 100% 67

AS-SET

AS26104 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 21 are in fix.csv.

  • ROA: none9
  • Route object: none3
  • Route object: RIR6
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none200.142.160.0/21No ROA covers it. Add a ROA for AS26104, maxLength 21.670 of 673
Route object: none200.142.160.0/21No route object for it. Add a route object with origin AS26104 in the RIR database for the space.670 of 673
ROA: none2804:4234::/33No ROA covers it. Add a ROA for AS26104, maxLength 33.2 of 636
Route object: none2804:4234::/33No route object for it. Add a route object with origin AS26104 in the RIR database for the space.2 of 636
ROA: none2804:4234::/40No ROA covers it. Add a ROA for AS26104, maxLength 40.2 of 636
Route object: none2804:4234::/40No route object for it. Add a route object with origin AS26104 in the RIR database for the space.2 of 636
ROA: none200.142.169.0/24No ROA covers it. Add a ROA for AS26104, maxLength 24.671 of 673
Route object: RIR200.142.169.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none200.142.170.0/24No ROA covers it. Add a ROA for AS26104, maxLength 24.671 of 673
Route object: RIR200.142.170.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none200.142.172.0/24No ROA covers it. Add a ROA for AS26104, maxLength 24.671 of 673
Route object: RIR200.142.172.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none200.142.173.0/24No ROA covers it. Add a ROA for AS26104, maxLength 24.671 of 673
Route object: RIR200.142.173.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none200.142.174.0/24No ROA covers it. Add a ROA for AS26104, maxLength 24.671 of 673
Route object: RIR200.142.174.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none200.142.175.0/24No ROA covers it. Add a ROA for AS26104, maxLength 24.671 of 673
Route object: RIR200.142.175.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673

Route objects not announced

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

200.142.168.0/21RADBNo ROA
2804:4234:8000::/33RADBNo ROA
2804:4234:8000::/48RADBNo 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.