bgpreport

Network · data from 2026-11-12

AS218616 HALISTON-AS HALISTON LIMITED

Registry name: HALISTON-AS HALISTON LIMITED, GB · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS218616, 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.

13.141.121.0/24 Invalid: origin Other origin only 2 0%low visibility 1
13.141.127.0/24 Invalid: origin Other origin only 2 0%low visibility 1
79.176.105.0/24 Invalid: origin Other origin only 2 0%low visibility 1
82.108.173.0/24 Invalid: origin Other origin only 2 0%low visibility 1
154.196.163.0/24 Valid RIR databaseAFRINIC, RADB 404 60% 63

AS-SET

AS218616 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: origin4
  • Route object: none4
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: origin13.141.121.0/24ROAs covering it name AS834, not AS218616. If AS218616 should announce it, add a ROA for AS218616.2 of 673
Route object: none13.141.121.0/24Route objects for it name AS834. Add a route object with origin AS218616 in the RIR database for the space.2 of 673
ROA: origin13.141.127.0/24ROAs covering it name AS834, not AS218616. If AS218616 should announce it, add a ROA for AS218616.2 of 673
Route object: none13.141.127.0/24Route objects for it name AS834. Add a route object with origin AS218616 in the RIR database for the space.2 of 673
ROA: origin79.176.105.0/24ROAs covering it name AS834, not AS218616. If AS218616 should announce it, add a ROA for AS218616.2 of 673
Route object: none79.176.105.0/24Route objects for it name AS834. Add a route object with origin AS218616 in the RIR database for the space.2 of 673
ROA: origin82.108.173.0/24ROAs covering it name AS834, not AS218616. If AS218616 should announce it, add a ROA for AS218616.2 of 673
Route object: none82.108.173.0/24Route objects for it name AS834, AS3257. Add a route object with origin AS218616 in the RIR database for the space.2 of 673

Route objects not announced

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

154.196.161.0/24AFRINIC, RADBValid
156.230.0.0/24AFRINIC, RADBValid
2a0a:87c0:fffc::/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.