bgpreport

Network · data from 2026-11-12

AS137076 TTSL-AS-BB - TTSL-ISP DIVISION

Registry name: TTSL-AS-BB - TTSL-ISP DIVISION, IN · not in PeeringDB

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

Announced routes

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

14.96.32.0/23 Valid RIR databaseAPNIC 671 100% 67
14.96.34.0/23 Valid RIR databaseAPNIC 671 100% 67
14.96.40.0/23 Valid RIR databaseAPNIC 671 100% 67
14.96.44.0/23 Valid RIR databaseAPNIC 671 100% 67
14.96.46.0/23 Valid RIR databaseAPNIC 671 100% 67
14.96.24.0/23 Valid RIR databaseAPNIC 670 100% 67
14.96.26.0/23 Valid RIR databaseAPNIC 670 100% 67
14.96.28.0/23 Valid RIR databaseAPNIC 670 100% 67
14.96.30.0/23 Valid RIR databaseAPNIC 670 100% 67
14.96.36.0/23 Valid RIR databaseAPNIC 670 100% 66

AS-SET

AS137076 isn't in PeeringDB, where networks name their 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 35 are in fix.csv.

  • Route object: not announced35

Route objects not announced

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

14.96.24.0/21APNICValid
14.96.24.0/22APNICValid
14.96.24.0/24APNICValid
14.96.25.0/24APNICValid
14.96.26.0/24APNICValid
14.96.27.0/24APNICValid
14.96.28.0/22APNICValid
14.96.28.0/24APNICValid
14.96.29.0/24APNICValid
14.96.30.0/24APNICValid
14.96.31.0/24APNICValid
14.96.32.0/21APNICValid
14.96.32.0/22APNICValid
14.96.32.0/24APNICValid
14.96.33.0/24APNICValid
14.96.34.0/24APNICValid
14.96.35.0/24APNICValid
14.96.36.0/22APNICValid
14.96.36.0/24APNICValid
14.96.37.0/24APNICValid
14.96.38.0/23APNICValid
14.96.38.0/24APNICValid
14.96.39.0/24APNICValid
14.96.40.0/21APNICValid
14.96.40.0/22APNICValid
14.96.40.0/24APNICValid
14.96.41.0/24APNICValid
14.96.42.0/23APNICValid
14.96.42.0/24APNICValid
14.96.43.0/24APNICValid
14.96.44.0/22APNICValid
14.96.44.0/24APNICValid
14.96.45.0/24APNICValid
14.96.46.0/24APNICValid
14.96.47.0/24APNICValid

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.