bgpreport

Network · data from 2026-11-12

AS137515 FRC

Registry name: FRC-AP - Md. Raisul Islam, BD · PeeringDB

7IPv4 routes 100.0% RPKI valid · 100.0% with a route object
17IPv6 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
2Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS137515, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS137515, 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.111.120.0/22 Valid RIR databaseAPNIC 672 100% 67
103.111.120.0/24 Valid RIR databaseAPNIC 672 100% 67
103.111.121.0/24 Valid RIR databaseAPNIC 672 100% 67
103.111.122.0/24 Valid RIR databaseAPNIC 672 100% 67
103.111.123.0/24 Valid RIR databaseAPNIC 672 100% 67
2405:7e40::/32 Valid RIR databaseAPNIC 635 100% 69
2405:7e40::/36 Valid RIR databaseAPNIC 635 100% 69
2405:7e40:1000::/36 Valid RIR databaseAPNIC 635 100% 69
2405:7e40:2000::/36 Valid RIR databaseAPNIC 635 100% 69
2405:7e40:3000::/36 Valid RIR databaseAPNIC 635 100% 69
2405:7e40:4000::/36 Valid RIR databaseAPNIC 635 100% 69
2405:7e40:5000::/36 Valid RIR databaseAPNIC 635 100% 69
2405:7e40:6000::/36 Valid RIR databaseAPNIC 635 100% 69
2405:7e40:7000::/36 Valid RIR databaseAPNIC 635 100% 69
2405:7e40:8000::/36 Valid RIR databaseAPNIC 635 100% 69
2405:7e40:9000::/36 Valid RIR databaseAPNIC 635 100% 69
2405:7e40:a000::/36 Valid RIR databaseAPNIC 635 100% 69
2405:7e40:b000::/36 Valid RIR databaseAPNIC 635 100% 69
2405:7e40:c000::/36 Valid RIR databaseAPNIC 635 100% 69
2405:7e40:d000::/36 Valid RIR databaseAPNIC 635 100% 69
2405:7e40:e000::/36 Valid RIR databaseAPNIC 635 100% 69
2405:7e40:f000::/36 Valid RIR databaseAPNIC 635 100% 69
103.111.120.0/23 Valid RIR databaseAPNIC 2 0%low visibility 3
103.111.122.0/23 Valid RIR databaseAPNIC 2 0%low visibility 3

AS-SET

PeeringDB's irr_as_set for AS137515: AS-137515. 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 (AS137515 isn't in the set, or no route object for AS137515 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 objectsAS137515 in itNot covered
AS-137515 APNIC 3130 Yes 0

Fix list

Nothing to change: every route is RPKI valid with a route object in an RIR database, and every route object is announced.

Route objects not announced

Every route object with origin AS137515 is announced.

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.