bgpreport

Network · data from 2026-11-12

AS135189 I connect broadband support and services

Registry name: ICONIN-AS - I connect broadband support and services, IN · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS135189, 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.54.104.0/24 Invalid: origin Other origin only 5 1%low visibility 2
2401:d660::/32 Valid RIR databaseAPNIC 636 100% 69
45.249.252.0/24 Valid RIR databaseAPNIC 2 0%low visibility 2
45.249.253.0/24 Valid RIR databaseAPNIC 2 0%low visibility 2
45.249.254.0/24 Valid RIR databaseAPNIC 2 0%low visibility 2
45.249.255.0/24 Valid RIR databaseAPNIC 2 0%low visibility 2

AS-SET

AS135189'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 12 are in fix.csv.

  • ROA: origin1
  • Route object: none1
  • Route object: not announced10
ChangePrefix or setDetailFull-table peers
ROA: origin103.54.104.0/24ROAs covering it name AS24554, AS55352, not AS135189. If AS135189 should announce it, add a ROA for AS135189.5 of 673
Route object: none103.54.104.0/24Route objects for it name AS24554, AS55352. Add a route object with origin AS135189 in the RIR database for the space.5 of 673

Route objects not announced

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

45.249.252.0/22APNICValid
45.249.252.0/23APNICValid
45.249.254.0/23APNICValid
103.219.0.0/22APNICValid
103.219.0.0/23APNICValid
103.219.0.0/24APNICValid
103.219.1.0/24APNICValid
103.219.2.0/23APNICValid
103.219.2.0/24APNICValid
103.219.3.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.