bgpreport

Network · data from 2026-11-12

AS136714 Stampede Communications

Registry name: STAMPEDE-AS - Stampede Communications Pvt. Ltd., IN · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS136714, 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.
2403:d4c0:8000::/33 Valid Nonecovered by 2403:d4c0::/32 635 100% 67
178.248.119.0/24 Valid Other IRR onlyRADB 673 100% 67
178.248.112.0/23 Valid Other IRR onlyRADB 672 100% 67
178.248.114.0/23 Valid Other IRR onlyRADB 671 100% 67
103.104.44.0/22 Valid RIR databaseAPNIC 673 100% 66
103.104.45.0/24 Valid RIR databaseAPNIC 673 100% 67
178.248.116.0/23 Valid RIR databaseRIPE 673 100% 66
178.248.118.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
103.104.46.0/23 Valid RIR databaseAPNIC 672 100% 67
178.248.112.0/21 Valid RIR databaseRIPE 672 100% 66
178.248.112.0/22 Valid RIR databaseRADB, RIPE 672 100% 67
103.104.47.0/24 Valid RIR databaseAPNIC 671 100% 67
2403:d4c0::/32 Valid RIR databaseAPNIC, RADB 635 100% 67
178.248.116.0/22 Valid RIR databaseRIPE 2 0%low visibility 2
103.104.46.0/24 Valid RIR databaseAPNIC 1 0%low visibility 2
178.248.114.0/24 Valid RIR databaseRADB, RIPE 1 0%low visibility 2
178.248.115.0/24 Valid RIR databaseRADB, RIPE 1 0%low visibility 2

AS-SET

AS136714'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 12 are in fix.csv.

  • Route object: none1
  • Route object: RIR3
  • Route object: not announced8
ChangePrefix or setDetailFull-table peers
Route object: none2403:d4c0:8000::/33No route object for it. A route object for 2403:d4c0::/32 with origin AS136714 covers it (filters allowing more-specifics accept it). Add a route object with origin AS136714 in the RIR database for the space.635 of 636
Route object: RIR178.248.119.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR178.248.112.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR178.248.114.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673

Route objects not announced

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

103.104.44.0/23APNICValid
103.104.44.0/24APNICValid
178.248.112.0/24RADB, RIPEValid
178.248.113.0/24RADB, RIPEValid
178.248.116.0/24RIPEValid
178.248.117.0/24RIPEValid
178.248.118.0/23RADBValid
2403:d4c0:4000::/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.