bgpreport

Network · data from 2026-11-12

AS8818 Tusass A/S

Registry name: Tusass A/S, GL · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS8818, 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.
46.16.16.0/21 No ROA RIR databaseRIPE 673 100% 67
185.18.188.0/22 No ROA RIR databaseRIPE 673 100% 67
185.21.228.0/22 No ROA RIR databaseRIPE 673 100% 67
185.93.20.0/22 No ROA RIR databaseRIPE 673 100% 67
185.157.200.0/22 No ROA RIR databaseRIPE 673 100% 67
2a03:fdc0::/32 No ROA RIR databaseRIPE 636 100% 67
88.83.24.0/21 Valid Nonecovered by 88.83.0.0/19 673 100% 67
37.18.44.0/22 Valid RIR databaseRIPE 673 100% 67
37.230.164.0/22 Valid RIR databaseRIPE 673 100% 67
37.230.214.0/23 Valid RIR databaseRIPE 673 100% 67
37.230.216.0/22 Valid RIR databaseRIPE 673 100% 67
37.230.220.0/23 Valid RIR databaseRIPE 673 100% 67
88.83.0.0/19 Valid RIR databaseRIPE 673 100% 67
178.170.132.0/22 Valid RIR databaseRIPE 673 100% 67
178.170.147.0/24 Valid RIR databaseRIPE 673 100% 67
178.170.160.0/22 Valid RIR databaseRIPE 673 100% 67
178.170.199.0/24 Valid RIR databaseRIPE 673 100% 67
178.170.200.0/22 Valid RIR databaseRIPE 673 100% 67
178.170.204.0/23 Valid RIR databaseRIPE 673 100% 67
178.170.210.0/23 Valid RIR databaseRIPE 673 100% 67
178.170.212.0/22 Valid RIR databaseRIPE 673 100% 67
178.170.216.0/24 Valid RIR databaseRIPE 673 100% 67
185.57.160.0/22 Valid RIR databaseRIPE 673 100% 67
188.72.71.0/24 Valid RIR databaseRIPE 673 100% 67
46.243.151.0/24 Valid RIR databaseRIPE 672 100% 67
128.0.70.0/24 Valid RIR databaseRIPE 672 100% 67
194.177.224.0/19 Valid RIR databaseRIPE 670 100% 67
2a00:1fa8::/32 Valid RIR databaseRIPE 636 100% 67

AS-SET

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

  • ROA: none6
  • Route object: none1
ChangePrefix or setDetailFull-table peers
ROA: none46.16.16.0/21No ROA covers it. Add a ROA for AS8818, maxLength 21.673 of 673
ROA: none185.18.188.0/22No ROA covers it. Add a ROA for AS8818, maxLength 22.673 of 673
ROA: none185.21.228.0/22No ROA covers it. Add a ROA for AS8818, maxLength 22.673 of 673
ROA: none185.93.20.0/22No ROA covers it. Add a ROA for AS8818, maxLength 22.673 of 673
ROA: none185.157.200.0/22No ROA covers it. Add a ROA for AS8818, maxLength 22.673 of 673
ROA: none2a03:fdc0::/32No ROA covers it. Add a ROA for AS8818, maxLength 32.636 of 636
Route object: none88.83.24.0/21No route object for it. A route object for 88.83.0.0/19 with origin AS8818 covers it (filters allowing more-specifics accept it). Add a route object with origin AS8818 in the RIR database for the space.673 of 673

Route objects not announced

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