bgpreport

Network · data from 2026-11-12

AS149573 SERVERAS-AS-IN - Serverwala Cloud Datacenters Private Limited

Registry name: SERVERAS-AS-IN - Serverwala Cloud Datacenters Private Limited, IN · not in PeeringDB

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

Announced routes

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

195.58.131.0/24 Invalid: origin Other origin only 155 23% 55
82.153.123.0/24 Invalid: origin Other origin only 139 21% 54
145.79.163.0/24 Invalid: origin Other origin only 10 1%low visibility 4
178.83.47.0/24 Invalid: origin Other origin only 2 0%low visibility 2
144.225.27.0/24 No ROA None 2 0%low visibility 2
217.145.69.0/24 Valid Other IRR onlyRADB 672 100% 66
103.131.25.0/24 Valid RIR databaseAPNIC 673 100% 66
103.183.157.0/24 Valid RIR databaseAPNIC 673 100% 66
151.242.51.0/24 Valid RIR databaseRADB, RIPE 673 100% 66
151.243.12.0/24 Valid RIR databaseRADB, RIPE 673 100% 66
151.243.98.0/24 Valid RIR databaseRADB, RIPE 673 100% 66
5.178.98.0/24 Valid RIR databaseRIPE 672 100% 66
103.131.24.0/24 Valid RIR databaseAPNIC 672 100% 66
103.131.26.0/24 Valid RIR databaseAPNIC 672 100% 66
140.99.208.0/24 Valid RIR databaseARIN, RADB 672 100% 66
185.209.75.0/24 Valid RIR databaseRADB, RIPE 672 100% 66
192.177.75.0/24 Valid RIR databaseARIN, RADB 672 100% 66

AS-SET

AS149573 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 15 are in fix.csv.

  • ROA: origin4
  • ROA: none1
  • Route object: none5
  • Route object: RIR1
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: origin195.58.131.0/24ROAs covering it name AS834, not AS149573. If AS149573 should announce it, add a ROA for AS149573.155 of 673
Route object: none195.58.131.0/24Route objects for it name AS834. Add a route object with origin AS149573 in the RIR database for the space.155 of 673
ROA: origin82.153.123.0/24ROAs covering it name AS834, AS8851, AS19905, AS206509, not AS149573. If AS149573 should announce it, add a ROA for AS149573.139 of 673
Route object: none82.153.123.0/24Route objects for it name AS834. Add a route object with origin AS149573 in the RIR database for the space.139 of 673
ROA: origin145.79.163.0/24ROAs covering it name AS267201, not AS149573. If AS149573 should announce it, add a ROA for AS149573.10 of 673
Route object: none145.79.163.0/24Route objects for it name AS267201. Add a route object with origin AS149573 in the RIR database for the space.10 of 673
ROA: origin178.83.47.0/24ROAs covering it name AS834, not AS149573. If AS149573 should announce it, add a ROA for AS149573.2 of 673
Route object: none178.83.47.0/24Route objects for it name AS834. Add a route object with origin AS149573 in the RIR database for the space.2 of 673
ROA: none144.225.27.0/24No ROA covers it. Add a ROA for AS149573, maxLength 24.2 of 673
Route object: none144.225.27.0/24No route object for it. Add a route object with origin AS149573 in the RIR database for the space.2 of 673
Route object: RIR217.145.69.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

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

103.131.24.0/23APNICValid
103.183.156.0/23APNICValid
103.183.156.0/24APNICValid
2400:54a0:20b0::/48APNICValid

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.