bgpreport

Network · data from 2026-11-12

AS58688 Radiant Communications Bangladesh

Registry name: RADIANT - RADIANT COMMUNICATIONS LTD IIG, BD · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS58688, 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.
45.112.73.0/24 Invalid: origin Other origin only 0 0%low visibility 1
103.217.112.0/22 Valid None 134 20% 47
103.20.180.0/22 Valid RIR databaseAPNIC 673 100% 66
103.20.180.0/23 Valid RIR databaseAPNIC 673 100% 66
103.20.182.0/23 Valid RIR databaseAPNIC 673 100% 66
103.247.44.0/22 Valid RIR databaseAPNIC 673 100% 66
103.247.45.0/24 Valid RIR databaseAPNIC 673 100% 66
103.247.46.0/24 Valid RIR databaseAPNIC 10 1%low visibility 5
103.20.180.0/24 Valid RIR databaseAPNIC 0 0%low visibility 1

AS-SET

AS58688'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 15 are in fix.csv.

  • ROA: origin1
  • Route object: none2
  • Route object: not announced12
ChangePrefix or setDetailFull-table peers
ROA: origin45.112.73.0/24ROAs covering it name AS38067, not AS58688. If AS58688 should announce it, add a ROA for AS58688.0 of 673
Route object: none45.112.73.0/24Route objects for it name AS38067. Add a route object with origin AS58688 in the RIR database for the space.0 of 673
Route object: none103.217.112.0/22No route object for it. Add a route object with origin AS58688 in the RIR database for the space.134 of 673

Route objects not announced

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

103.20.181.0/24APNICValid
103.20.182.0/24APNICValid
103.20.183.0/24APNICValid
103.217.113.0/24APNICValid
103.217.114.0/23APNICValid
103.217.114.0/24APNICValid
103.217.115.0/24APNICValid
103.247.44.0/23APNICValid
103.247.44.0/24APNICValid
103.247.46.0/23APNICValid
103.247.47.0/24APNICValid
2405:6900:f000::/36APNICValid

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.