bgpreport

Network · data from 2026-11-12

AS35052 AS_AT_TLD_SERVICES ACONET

Registry name: AS_AT_TLD_SERVICES ACONET, AT · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS35052, 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.
192.76.243.0/24 No ROA RIR databaseRIPE 673 100% 67
192.92.125.0/24 No ROA RIR databaseRIPE 671 100% 67
2001:678:1c::/48 Valid RIR databaseRIPE 635 100% 69
2001:67c:133c::/48 Valid RIR databaseRADB, RIPE 635 100% 70

AS-SET

AS35052 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 2 are in fix.csv.

  • ROA: none2
ChangePrefix or setDetailFull-table peers
ROA: none192.76.243.0/24No ROA covers it. Add a ROA for AS35052, maxLength 24.673 of 673
ROA: none192.92.125.0/24No ROA covers it. Add a ROA for AS35052, maxLength 24.671 of 673

Route objects not announced

Every route object with origin AS35052 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.