bgpreport

Network · data from 2026-11-12

AS215858 Delta-Telecom-DC Delta Telecom Ltd

Registry name: Delta-Telecom-DC Delta Telecom Ltd, AZ · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS215858, 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.
89.37.17.0/24 Valid RIR databaseRIPE 673 100% 66
89.37.18.0/24 Valid RIR databaseRIPE 673 100% 66
89.37.19.0/24 Valid RIR databaseRIPE 673 100% 66
89.37.20.0/24 Valid RIR databaseRIPE 673 100% 66
89.37.21.0/24 Valid RIR databaseRIPE 673 100% 66
89.37.22.0/24 Valid RIR databaseRIPE 673 100% 66
89.37.23.0/24 Valid RIR databaseRIPE 673 100% 66
89.37.16.0/24 Valid RIR databaseRIPE 15 2%low visibility 10

AS-SET

AS215858 isn't in PeeringDB, where networks name their AS-SET.

Fix list

Nothing to change: every route is RPKI valid with a route object in an RIR database, and every route object is announced.

Route objects not announced

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