bgpreport

Network · data from 2026-11-12

AS141723 BEE ONLINE

Registry name: BEEONLINE-AS-AP - BEE ONLINE, BD · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS141723, 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.162.187.0/24 Valid RIR databaseAPNIC 673 100% 67
103.104.243.0/24 Valid RIR databaseAPNIC 672 100% 69
103.146.57.0/24 Valid RIR databaseAPNIC 672 100% 69
103.162.186.0/24 Valid RIR databaseAPNIC 672 100% 67
2407:1d40::/32 Valid RIR databaseAPNIC 635 100% 67
103.162.186.0/23 Valid RIR databaseAPNIC 42 6%low visibility 29

AS-SET

AS141723'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 20 are in fix.csv.

  • Route object: not announced20

Route objects not announced

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

2404:3d40:100::/48APNICValid
2407:1d40::/36APNICValid
2407:1d40:1::/48APNICValid
2407:1d40:2::/48APNICValid
2407:1d40:3::/48APNICValid
2407:1d40:4::/48APNICValid
2407:1d40:5::/48APNICValid
2407:1d40:6::/48APNICValid
2407:1d40:7::/48APNICValid
2407:1d40:8::/48APNICValid
2407:1d40:9::/48APNICValid
2407:1d40:a::/48APNICValid
2407:1d40:b::/48APNICValid
2407:1d40:c::/48APNICValid
2407:1d40:d::/48APNICValid
2407:1d40:e::/48APNICValid
2407:1d40:f::/48APNICValid
2407:1d40:1000::/36APNICValid
2407:1d40:1000::/48APNICValid
2407:1d40:1001::/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.