bgpreport

Network · data from 2026-11-12

AS133605 Bright Technologies Limited

Registry name: BTL-BD - Bright Technologies Limited, BD · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS133605, 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.252.127.0/24 Invalid: origin Other origin only 3 0%low visibility 3
103.253.177.0/24 Valid RIR databaseAPNIC 672 100% 67
144.79.217.0/24 Valid RIR databaseAPNIC 672 100% 67
163.227.145.0/24 Valid RIR databaseAPNIC 672 100% 67
163.227.144.0/24 Valid RIR databaseAPNIC 669 99% 67

AS-SET

AS133605'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 36 are in fix.csv.

  • ROA: origin1
  • Route object: none1
  • Route object: not announced34
ChangePrefix or setDetailFull-table peers
ROA: origin103.252.127.0/24ROAs covering it name AS138596, not AS133605. If AS133605 should announce it, add a ROA for AS133605.3 of 673
Route object: none103.252.127.0/24Route objects for it name AS138596. Add a route object with origin AS133605 in the RIR database for the space.3 of 673

Route objects not announced

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

103.121.77.0/24APNICValid
103.121.79.0/24APNICValid
157.10.239.0/24APNICInvalid: origin
2401:2cc0::/32APNICValid
2401:2cc0::/33APNICValid
2401:2cc0::/34APNICValid
2401:2cc0::/35APNICValid
2401:2cc0::/36APNICValid
2401:2cc0:1000::/36APNICValid
2401:2cc0:2000::/35APNICValid
2401:2cc0:2000::/36APNICValid
2401:2cc0:3000::/36APNICValid
2401:2cc0:4000::/34APNICValid
2401:2cc0:4000::/35APNICValid
2401:2cc0:4000::/36APNICValid
2401:2cc0:5000::/36APNICValid
2401:2cc0:6000::/35APNICValid
2401:2cc0:6000::/36APNICValid
2401:2cc0:7000::/36APNICValid
2401:2cc0:8000::/33APNICValid
2401:2cc0:8000::/34APNICValid
2401:2cc0:8000::/35APNICValid
2401:2cc0:8000::/36APNICValid
2401:2cc0:9000::/36APNICValid
2401:2cc0:a000::/35APNICValid
2401:2cc0:a000::/36APNICValid
2401:2cc0:b000::/36APNICValid
2401:2cc0:c000::/34APNICValid
2401:2cc0:c000::/35APNICValid
2401:2cc0:c000::/36APNICValid
2401:2cc0:d000::/36APNICValid
2401:2cc0:e000::/35APNICValid
2401:2cc0:e000::/36APNICValid
2401:2cc0: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.