bgpreport

Network · data from 2026-11-12

AS215030 AspireHosting

Registry name: AspireHosting Budankailu Namrata Patra trading as AspireHosting, IN · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS215030, 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.
82.41.64.0/24 Valid RIR databaseRADB, RIPE 673 100% 66
82.41.67.0/24 Valid RIR databaseRADB, RIPE 670 100% 66
62.41.26.0/24 Valid RIR databaseRADB, RIPE 667 99% 67
89.106.84.0/24 Valid RIR databaseRIPE 667 99% 67
77.67.1.0/24 Valid RIR databaseRADB, RIPE 660 98% 67
2a06:9801:1201::/48 Valid RIR databaseRIPE 631 99% 69
2a06:9801:1200::/48 Valid RIR databaseRIPE 630 99% 67

AS-SET

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

  • Route object: not announced5

Route objects not announced

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

2a06:1283:8906::/48RIPEValid
2a06:1283:8907::/48RIPEValid
2a10:fa82:f200::/40RIPEValid
2a10:fa82:f210::/44RIPEValid
2a13:9500:14c::/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.