bgpreport

Network · data from 2026-11-12

AS21060 ASN-ATEA-DK Atea A/S

Registry name: ASN-ATEA-DK Atea A/S, DK · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS21060, 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.
194.116.222.0/24 No ROA Other origin only 673 100% 67
193.183.18.0/24 No ROA RIR databaseRIPE 673 100% 66
80.89.18.0/23 Valid Nonecovered by 80.89.16.0/20 673 100% 66
178.20.220.0/24 Valid Other origin only 673 100% 66
80.89.30.0/24 Valid Nonecovered by 80.89.16.0/20 672 100% 66
80.82.96.0/20 Valid RIR databaseRIPE 673 100% 66
80.89.16.0/20 Valid RIR databaseRIPE 673 100% 66
91.195.58.0/23 Valid RIR databaseRIPE 673 100% 66
91.213.70.0/24 Valid RIR databaseRIPE 673 100% 66
92.43.232.0/21 Valid RIR databaseRIPE 673 100% 66
178.20.216.0/24 Valid RIR databaseRIPE 673 100% 66
178.20.217.0/24 Valid RIR databaseRIPE 673 100% 66
178.20.218.0/24 Valid RIR databaseRIPE 673 100% 66
178.20.223.0/24 Valid RIR databaseRIPE 673 100% 66
185.126.52.0/24 Valid RIR databaseRIPE 673 100% 66
185.134.252.0/22 Valid RIR databaseRIPE 673 100% 66
185.155.36.0/22 Valid RIR databaseRIPE 673 100% 66
188.244.64.0/20 Valid RIR databaseRIPE 673 100% 66
194.8.244.0/23 Valid RIR databaseRIPE 673 100% 66
2a01:7cc0:100::/40 Valid RIR databaseRIPE 635 100% 67
2a02:7c00::/32 Valid RIR databaseRIPE 635 100% 67

AS-SET

AS21060 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 11 are in fix.csv.

  • ROA: none2
  • Route object: none4
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: none194.116.222.0/24No ROA covers it. Add a ROA for AS21060, maxLength 24.673 of 673
Route object: none194.116.222.0/24Route objects for it name AS31027. Add a route object with origin AS21060 in the RIR database for the space.673 of 673
ROA: none193.183.18.0/24No ROA covers it. Add a ROA for AS21060, maxLength 24.673 of 673
Route object: none80.89.18.0/23No route object for it. A route object for 80.89.16.0/20 with origin AS21060 covers it (filters allowing more-specifics accept it). Add a route object with origin AS21060 in the RIR database for the space.673 of 673
Route object: none178.20.220.0/24Route objects for it name AS31027, AS42553. Add a route object with origin AS21060 in the RIR database for the space.673 of 673
Route object: none80.89.30.0/24No route object for it. A route object for 80.89.16.0/20 with origin AS21060 covers it (filters allowing more-specifics accept it). Add a route object with origin AS21060 in the RIR database for the space.672 of 673

Route objects not announced

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

92.43.232.0/24RIPEInvalid: maxLength
92.43.233.0/24RIPEInvalid: maxLength
193.105.44.0/24RIPEValid
193.183.18.0/23RIPENo ROA
2a02:6c0:1::/48RIPENo 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.