bgpreport

Network · data from 2026-11-12

AS203516 AltunHOST

Registry name: AltunHOST AltunHOST LTD, GB · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS203516, 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.232.237.0/24 Invalid: origin Other origin only 2 0%low visibility 2
2.58.153.0/24 No ROA None 2 0%low visibility 2
2.58.155.0/24 No ROA None 2 0%low visibility 2
5.175.136.0/24 Valid RIR databaseRIPE 673 100% 67
5.175.206.0/24 Valid RIR databaseRIPE 673 100% 67
5.230.9.0/24 Valid RIR databaseRIPE 673 100% 67
89.144.10.0/24 Valid RIR databaseRIPE 673 100% 67
89.144.20.0/24 Valid RIR databaseRIPE 673 100% 67
194.146.47.0/24 Valid RIR databaseRIPE 673 100% 67
5.83.135.0/24 Valid RIR databaseRIPE 671 100% 68
5.83.131.0/24 Valid RIR databaseRIPE 669 99% 67
2a02:2fc0:12::/48 Valid RIR databaseRIPE 634 100% 67
2a02:2fc0:2c::/48 Valid RIR databaseRIPE 633 100% 69

AS-SET

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

  • ROA: origin1
  • ROA: none2
  • Route object: none3
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: origin46.232.237.0/24ROAs covering it name AS218538, not AS203516. If AS203516 should announce it, add a ROA for AS203516.2 of 673
Route object: none46.232.237.0/24Route objects for it name AS218538. Add a route object with origin AS203516 in the RIR database for the space.2 of 673
ROA: none2.58.153.0/24No ROA covers it. Add a ROA for AS203516, maxLength 24.2 of 673
Route object: none2.58.153.0/24No route object for it. Add a route object with origin AS203516 in the RIR database for the space.2 of 673
ROA: none2.58.155.0/24No ROA covers it. Add a ROA for AS203516, maxLength 24.2 of 673
Route object: none2.58.155.0/24No route object for it. Add a route object with origin AS203516 in the RIR database for the space.2 of 673

Route objects not announced

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

2a02:2fc0:2b::/48RIPEValid

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.