bgpreport

Network · data from 2026-11-12

AS137425 Incomit Solution

Registry name: INCOMITSOLUTION-AS-AP - INCOMIT SOLUTION, BD · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS137425, 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.
59.153.29.0/24 Invalid: origin Other origin only 1 0%low visibility 1
103.108.60.0/24 Valid RIR databaseAPNIC 673 100% 67
103.108.62.0/24 Valid RIR databaseAPNIC 673 100% 67
103.108.63.0/24 Valid RIR databaseAPNIC 673 100% 69
103.127.86.0/24 Valid RIR databaseAPNIC 673 100% 67
160.30.63.0/24 Valid RIR databaseAPNIC 673 100% 69
103.108.61.0/24 Valid RIR databaseAPNIC 672 100% 67
103.127.84.0/24 Valid RIR databaseAPNIC 671 100% 67
157.10.134.0/24 Valid RIR databaseAPNIC 671 100% 67
2406:ebc0:3000::/36 Valid RIR databaseAPNIC 636 100% 70
2406:ebc0::/32 Valid RIR databaseAPNIC 635 100% 69
2406:ebc0:1000::/36 Valid RIR databaseAPNIC 635 100% 69
2406:ebc0:2000::/36 Valid RIR databaseAPNIC 635 100% 69
2406:ebc0:4000::/36 Valid RIR databaseAPNIC 635 100% 69
2406:ebc0:5000::/36 Valid RIR databaseAPNIC 635 100% 69
2406:ebc0::/36 Valid RIR databaseAPNIC 634 100% 69
2406:ebc0:1::/48 Valid RIR databaseAPNIC 634 100% 69
2406:ebc0:2::/48 Valid RIR databaseAPNIC 634 100% 69
103.108.60.0/22 Valid RIR databaseAPNIC 1 0%low visibility 2

AS-SET

PeeringDB's irr_as_set for AS137425: AS137425:AS-INCOMIT. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS137425 isn't in the set, or no route object for AS137425 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS137425 in itNot covered
AS137425:AS-INCOMIT In no IRR database read today.

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: origin1
  • Route object: none1
  • AS-SET: not found1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: origin59.153.29.0/24ROAs covering it name AS134128, not AS137425. If AS137425 should announce it, add a ROA for AS137425.1 of 673
Route object: none59.153.29.0/24Route objects for it name AS134128. Add a route object with origin AS137425 in the RIR database for the space.1 of 673
AS-SET: not foundAS137425:AS-INCOMITPeeringDB names AS137425:AS-INCOMIT; no IRR database read has it.

Route objects not announced

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

103.108.60.0/23APNICValid
103.108.62.0/23APNICValid

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.