bgpreport

Network · data from 2026-11-12

AS150070 SPIRETEL-AS-IN - SPIRETEL TECHNOLOGIES PRIVATE LIMITED

Registry name: SPIRETEL-AS-IN - SPIRETEL TECHNOLOGIES PRIVATE LIMITED, IN · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS150070, 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.
103.185.204.0/24 No ROA Nonecovered by 103.185.204.0/23 10 1%low visibility 4
103.185.205.0/24 No ROA Nonecovered by 103.185.204.0/23 10 1%low visibility 4
103.185.204.0/23 No ROA RIR databaseAPNIC 672 100% 66
103.21.70.0/23 Valid RIR databaseAPNIC 672 100% 66
2001:df1:8e40::/48 Valid RIR databaseAPNIC 636 100% 70
103.21.70.0/24 Valid RIR databaseAPNIC 10 1%low visibility 4
103.21.71.0/24 Valid RIR databaseAPNIC 10 1%low visibility 4

AS-SET

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

  • ROA: none3
  • Route object: none2
ChangePrefix or setDetailFull-table peers
ROA: none103.185.204.0/24No ROA covers it. Add a ROA for AS150070, maxLength 24.10 of 673
Route object: none103.185.204.0/24No route object for it. A route object for 103.185.204.0/23 with origin AS150070 covers it (filters allowing more-specifics accept it). Add a route object with origin AS150070 in the RIR database for the space.10 of 673
ROA: none103.185.205.0/24No ROA covers it. Add a ROA for AS150070, maxLength 24.10 of 673
Route object: none103.185.205.0/24No route object for it. A route object for 103.185.204.0/23 with origin AS150070 covers it (filters allowing more-specifics accept it). Add a route object with origin AS150070 in the RIR database for the space.10 of 673
ROA: none103.185.204.0/23No ROA covers it. Add a ROA for AS150070, maxLength 23.672 of 673

Route objects not announced

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