bgpreport

Network · data from 2026-11-12

AS61578 AS61578 - ALIANCA SISTEMAS DE TELECOMUNICACOES

Registry name: AS61578 - ALIANCA SISTEMAS DE TELECOMUNICACOES, BR · not in PeeringDB

4IPv4 routes 0.0% RPKI valid · 0.0% with a route object
0IPv6 routes
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
2Route objects not announced registered with origin AS61578, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS61578, 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.
143.208.216.0/24 No ROA Nonecovered by 143.208.216.0/22 671 100% 67
143.208.217.0/24 No ROA Nonecovered by 143.208.216.0/22 671 100% 67
143.208.218.0/24 No ROA Nonecovered by 143.208.216.0/22 671 100% 67
143.208.219.0/24 No ROA Nonecovered by 143.208.216.0/22 671 100% 67

AS-SET

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

  • ROA: none4
  • Route object: none4
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none143.208.216.0/24No ROA covers it. Add a ROA for AS61578, maxLength 24.671 of 673
Route object: none143.208.216.0/24No route object for it. A route object for 143.208.216.0/22 with origin AS61578 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61578 in the RIR database for the space.671 of 673
ROA: none143.208.217.0/24No ROA covers it. Add a ROA for AS61578, maxLength 24.671 of 673
Route object: none143.208.217.0/24No route object for it. A route object for 143.208.216.0/22 with origin AS61578 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61578 in the RIR database for the space.671 of 673
ROA: none143.208.218.0/24No ROA covers it. Add a ROA for AS61578, maxLength 24.671 of 673
Route object: none143.208.218.0/24No route object for it. A route object for 143.208.216.0/22 with origin AS61578 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61578 in the RIR database for the space.671 of 673
ROA: none143.208.219.0/24No ROA covers it. Add a ROA for AS61578, maxLength 24.671 of 673
Route object: none143.208.219.0/24No route object for it. A route object for 143.208.216.0/22 with origin AS61578 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61578 in the RIR database for the space.671 of 673

Route objects not announced

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

143.208.216.0/22RADBNo ROA
2804:2b08::/32RADBNo 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.