bgpreport

Network · data from 2026-11-12

AS136555 BK Online

Registry name: BKONLINE-AS-AP - BK ONLINE, BD · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS136555, 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.79.219.0/24 Invalid: origin Other origin only 0 0%low visibility 1
103.195.0.0/24 Invalid: origin Other origin only 0 0%low visibility 1
103.195.1.0/24 Invalid: origin Other origin only 0 0%low visibility 1
103.195.2.0/24 Invalid: origin Other origin only 0 0%low visibility 1
103.195.3.0/24 Invalid: origin Other origin only 0 0%low visibility 1
103.92.153.0/24 Invalid: maxLength Other origin onlycovered by 103.92.152.0/23 0 0%low visibility 1
103.120.36.0/24 No ROA Other origin only 0 0%low visibility 1
103.92.154.0/24 Valid RIR databaseAPNIC 673 100% 70
103.92.152.0/24 Valid RIR databaseAPNIC 672 100% 67
103.92.155.0/24 Valid RIR databaseAPNIC 672 100% 67

AS-SET

AS136555'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 19 are in fix.csv.

  • ROA: origin5
  • ROA: maxLength1
  • ROA: none1
  • Route object: none7
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: origin103.79.219.0/24ROAs covering it name AS136010, not AS136555. If AS136555 should announce it, add a ROA for AS136555.0 of 673
Route object: none103.79.219.0/24Route objects for it name AS136010. Add a route object with origin AS136555 in the RIR database for the space.0 of 673
ROA: origin103.195.0.0/24ROAs covering it name AS137551, not AS136555. If AS136555 should announce it, add a ROA for AS136555.0 of 673
Route object: none103.195.0.0/24Route objects for it name AS137551. Add a route object with origin AS136555 in the RIR database for the space.0 of 673
ROA: origin103.195.1.0/24ROAs covering it name AS137551, not AS136555. If AS136555 should announce it, add a ROA for AS136555.0 of 673
Route object: none103.195.1.0/24Route objects for it name AS137551. Add a route object with origin AS136555 in the RIR database for the space.0 of 673
ROA: origin103.195.2.0/24ROAs covering it name AS137551, not AS136555. If AS136555 should announce it, add a ROA for AS136555.0 of 673
Route object: none103.195.2.0/24Route objects for it name AS137551. Add a route object with origin AS136555 in the RIR database for the space.0 of 673
ROA: origin103.195.3.0/24ROAs covering it name AS137551, not AS136555. If AS136555 should announce it, add a ROA for AS136555.0 of 673
Route object: none103.195.3.0/24Route objects for it name AS137551. Add a route object with origin AS136555 in the RIR database for the space.0 of 673
ROA: maxLength103.92.153.0/24ROA 103.92.152.0/22 AS136555 has maxLength 22; ROA 103.92.152.0/23 AS136555 has maxLength 23; the route is a /24. Raise the maxLength, or add a ROA for 103.92.153.0/24.0 of 673
Route object: none103.92.153.0/24Route objects for it name AS150774. A route object for 103.92.152.0/23 with origin AS136555 covers it (filters allowing more-specifics accept it). Add a route object with origin AS136555 in the RIR database for the space.0 of 673
ROA: none103.120.36.0/24No ROA covers it. Add a ROA for AS136555, maxLength 24.0 of 673
Route object: none103.120.36.0/24Route objects for it name AS834. Add a route object with origin AS136555 in the RIR database for the space.0 of 673

Route objects not announced

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

103.92.152.0/22APNICValid
103.92.152.0/23APNICValid
103.92.154.0/23APNICValid
2403:bb40::/32APNICValid
2403:bb40::/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.