bgpreport

Network · data from 2026-11-12

AS140687 ISEVEN-AS-AP - I Seven

Registry name: ISEVEN-AS-AP - I Seven, IN · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS140687, 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.26.11.0/24 Invalid: origin Other origin only 10 1%low visibility 7
2001:e48:42::/64 No ROA None 3 0%low visibility 2
103.67.236.0/24 Valid RIR databaseAPNIC 673 100% 66
103.67.237.0/24 Valid RIR databaseAPNIC 673 100% 66
103.67.238.0/24 Valid RIR databaseAPNIC 673 100% 66
103.67.239.0/24 Valid RIR databaseAPNIC 673 100% 66
103.182.210.0/24 Valid RIR databaseAPNIC 673 100% 66
103.182.211.0/24 Valid RIR databaseAPNIC 673 100% 66
115.84.170.0/24 Valid RIR databaseAPNIC 673 100% 66
115.84.171.0/24 Valid RIR databaseAPNIC 673 100% 66
151.158.206.0/24 Valid RIR databaseAPNIC 673 100% 66
151.158.207.0/24 Valid RIR databaseAPNIC 673 100% 66
192.232.50.0/24 Valid RIR databaseAPNIC 673 100% 66
192.232.51.0/24 Valid RIR databaseAPNIC 673 100% 66

AS-SET

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

  • ROA: origin1
  • ROA: none1
  • Route object: none2
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: origin103.26.11.0/24ROAs covering it name AS834, not AS140687. If AS140687 should announce it, add a ROA for AS140687.10 of 673
Route object: none103.26.11.0/24Route objects for it name AS834. Add a route object with origin AS140687 in the RIR database for the space.10 of 673
ROA: none2001:e48:42::/64No ROA covers it. Add a ROA for AS140687, maxLength 64.3 of 636
Route object: none2001:e48:42::/64No route object for it. Add a route object with origin AS140687 in the RIR database for the space.3 of 636

Route objects not announced

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

103.182.210.0/23APNICValid
115.84.170.0/23APNICValid
165.101.107.0/24APNICValid

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.