bgpreport

Network · data from 2026-11-12

AS205800 Steps Telecom

Registry name: STEPS-TELECOM-AS Steps Telecom For Internet Ltd., IQ · PeeringDB

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

Announced routes

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

122.102.119.0/24 Valid None 670 100% 68
5.10.226.0/24 Valid RIR databaseRIPE 671 100% 66
185.206.126.0/24 Valid RIR databaseRADB, RIPE 671 100% 68
185.206.125.0/24 Valid RIR databaseRADB, RIPE 670 100% 67
185.206.127.0/24 Valid RIR databaseRADB, RIPE 670 100% 67
185.206.124.0/24 Valid RIR databaseRADB, RIPE 669 99% 68
188.72.46.0/24 Valid RIR databaseRIPE 669 99% 68
202.164.207.0/24 Valid RIR databaseRIPE 669 99% 68
188.72.49.0/24 Valid RIR databaseRIPE 667 99% 67
188.72.41.0/24 Valid RIR databaseRIPE 666 99% 68

AS-SET

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

  • Route object: none1
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
Route object: none122.102.119.0/24No route object for it. Add a route object with origin AS205800 in the RIR database for the space.670 of 673

Route objects not announced

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

185.206.124.0/22RIPENo ROA
185.239.179.0/24RADB, RIPEValid
188.72.40.0/24RIPEValid
217.145.231.0/24RIPEValid
2a0b:d3c0::/32RIPEValid

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.