bgpreport

Network · data from 2026-11-12

AS139931 Bangladesh Submarine Cables Public Limited Company (BSCPLC)

Registry name: BANGLADESH-AS-AP - Bangladesh Submarine Cable Company Limited (BSCCL), BD · PeeringDB

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

Announced routes

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

163.47.80.0/22 Invalid: origin RIR databaseAPNIC 0 0%low visibility 1
163.47.80.0/24 Invalid: origin RIR databaseAPNIC 0 0%low visibility 1
163.47.81.0/24 Invalid: origin RIR databaseAPNIC 0 0%low visibility 1
163.47.83.0/24 Invalid: origin RIR databaseAPNIC 0 0%low visibility 1
103.16.152.0/24 Invalid: maxLength Other origin onlycovered by 103.16.152.0/22 6 1%low visibility 7
103.16.154.0/24 Invalid: maxLength Other origin onlycovered by 103.16.152.0/22 6 1%low visibility 7
103.16.155.0/24 Invalid: maxLength Other origin onlycovered by 103.16.152.0/22 6 1%low visibility 7
103.16.153.0/24 Valid RIR databaseAPNIC 71 11% 36

AS-SET

PeeringDB's irr_as_set for AS139931: APNIC::AS-SET-BSCCL. 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 (AS139931 isn't in the set, or no route object for AS139931 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 objectsAS139931 in itNot covered
APNIC::AS-SET-BSCCL APNIC 1,9547174,393 Yes 0

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: maxLength3
  • Route object: none3
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: origin163.47.80.0/22ROAs covering it name AS132602, not AS139931. If AS139931 should announce it, add a ROA for AS139931.0 of 673
ROA: origin163.47.80.0/24ROAs covering it name AS132602, not AS139931. If AS139931 should announce it, add a ROA for AS139931.0 of 673
ROA: origin163.47.81.0/24ROAs covering it name AS132602, not AS139931. If AS139931 should announce it, add a ROA for AS139931.0 of 673
ROA: origin163.47.83.0/24ROAs covering it name AS132602, not AS139931. If AS139931 should announce it, add a ROA for AS139931.0 of 673
ROA: maxLength103.16.152.0/24ROA 103.16.152.0/22 AS139931 has maxLength 22; the route is a /24. Raise the maxLength, or add a ROA for 103.16.152.0/24.6 of 673
Route object: none103.16.152.0/24Route objects for it name AS132602. A route object for 103.16.152.0/22 with origin AS139931 covers it (filters allowing more-specifics accept it). Add a route object with origin AS139931 in the RIR database for the space.6 of 673
ROA: maxLength103.16.154.0/24ROA 103.16.152.0/22 AS139931 has maxLength 22; the route is a /24. Raise the maxLength, or add a ROA for 103.16.154.0/24.6 of 673
Route object: none103.16.154.0/24Route objects for it name AS132602. A route object for 103.16.152.0/22 with origin AS139931 covers it (filters allowing more-specifics accept it). Add a route object with origin AS139931 in the RIR database for the space.6 of 673
ROA: maxLength103.16.155.0/24ROA 103.16.152.0/22 AS139931 has maxLength 22; the route is a /24. Raise the maxLength, or add a ROA for 103.16.155.0/24.6 of 673
Route object: none103.16.155.0/24Route objects for it name AS132602. A route object for 103.16.152.0/22 with origin AS139931 covers it (filters allowing more-specifics accept it). Add a route object with origin AS139931 in the RIR database for the space.6 of 673

Route objects not announced

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

103.16.152.0/22APNICValid
163.47.80.0/23APNICInvalid: origin
163.47.82.0/23APNICInvalid: origin
163.47.82.0/24APNICInvalid: origin
2406:4b00:a::/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.