bgpreport

Network · data from 2026-11-12

AS269517 Spacenet Telecom

Registry name: AS269517 - SPACENET PROVEDOR TELECOM LTDA, 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
2Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS269517, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS269517, 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.
45.188.74.0/23 Invalid: maxLength Nonecovered by 45.188.72.0/22 28 4%low visibility 10
45.188.72.0/22 Valid Other IRR onlyRADB, TC 671 100% 67
45.188.72.0/23 Valid Other IRR onlyRADB 671 100% 67
2804:65d4::/32 Valid Other IRR onlyRADB, TC 634 100% 67
45.188.73.0/24 Valid Other IRR onlyRADB, TC 209 31% 56
45.188.74.0/24 Valid Other IRR onlyTC 209 31% 56
45.188.75.0/24 Valid Other IRR onlyRADB, TC 209 31% 56
45.188.72.0/24 Valid Other IRR onlyRADB, TC 208 31% 56
2804:65d4::/38 Valid Other IRR onlyRADB 1 0%low visibility 1

AS-SET

AS269517'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 10 are in fix.csv.

  • ROA: maxLength1
  • Route object: none1
  • Route object: RIR8
ChangePrefix or setDetailFull-table peers
ROA: maxLength45.188.74.0/23ROA 45.188.72.0/22 AS269517 has maxLength 22; the route is a /23. Raise the maxLength, or add a ROA for 45.188.74.0/23.28 of 673
Route object: none45.188.74.0/23No route object for it. A route object for 45.188.72.0/22 with origin AS269517 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269517 in the RIR database for the space.28 of 673
Route object: RIR45.188.72.0/22Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR45.188.72.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR2804:65d4::/32Route object only in RADB, TC. Add it in the RIR database for the space.634 of 636
Route object: RIR45.188.73.0/24Route object only in RADB, TC. Add it in the RIR database for the space.209 of 673
Route object: RIR45.188.74.0/24Route object only in TC. Add it in the RIR database for the space.209 of 673
Route object: RIR45.188.75.0/24Route object only in RADB, TC. Add it in the RIR database for the space.209 of 673
Route object: RIR45.188.72.0/24Route object only in RADB, TC. Add it in the RIR database for the space.208 of 673
Route object: RIR2804:65d4::/38Route object only in RADB. Add it in the RIR database for the space.1 of 636

Route objects not announced

Every route object with origin AS269517 is announced.

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.