bgpreport

Network · data from 2026-11-12

AS132566 Skynet Internet Broadband

Registry name: SKYNET-AS-IN - Skynet Broadband Plus Solution, IN · PeeringDB

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

Announced routes

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

149.5.60.0/22 No ROA Other IRR onlyRADB 673 100% 66
149.5.60.0/23 No ROA Other IRR onlyRADB 673 100% 67
149.5.62.0/23 No ROA Other IRR onlyRADB 673 100% 67
149.5.60.0/24 No ROA Other IRR onlyRADB 43 6%low visibility 29
149.5.61.0/24 No ROA Other IRR onlyRADB 43 6%low visibility 29
149.5.62.0/24 No ROA Other IRR onlyRADB 43 6%low visibility 29
149.5.63.0/24 No ROA Other IRR onlyRADB 43 6%low visibility 29
103.19.128.0/23 Valid RIR databaseAPNIC 673 100% 66
103.84.68.0/22 Valid RIR databaseAPNIC 673 100% 66
103.84.68.0/23 Valid RIR databaseAPNIC 673 100% 66
103.84.70.0/23 Valid RIR databaseAPNIC 673 100% 66
103.230.226.0/23 Valid RIR databaseAPNIC 673 100% 66
202.66.176.0/22 Valid RIR databaseAPNIC 673 100% 66
202.66.176.0/23 Valid RIR databaseAPNIC 673 100% 66
202.66.178.0/23 Valid RIR databaseAPNIC 673 100% 66
2406:7340::/32 Valid RIR databaseAPNIC 636 100% 70
2406:7340:ffa0::/48 Valid RIR databaseAPNIC 636 100% 70
2406:7340:ffa1::/48 Valid RIR databaseAPNIC 636 100% 70
2406:7340:ffa4::/48 Valid RIR databaseAPNIC 636 100% 70
2406:7340:ffa5::/48 Valid RIR databaseAPNIC 636 100% 70
2406:7340:ffa6::/48 Valid RIR databaseAPNIC 636 100% 70
2406:7340:ffa2::/48 Valid RIR databaseAPNIC 635 100% 69
103.19.128.0/24 Valid RIR databaseAPNIC 43 6%low visibility 29
103.19.129.0/24 Valid RIR databaseAPNIC 43 6%low visibility 29
103.84.68.0/24 Valid RIR databaseAPNIC 43 6%low visibility 29
103.84.69.0/24 Valid RIR databaseAPNIC 43 6%low visibility 29
103.84.70.0/24 Valid RIR databaseAPNIC 43 6%low visibility 29
103.84.71.0/24 Valid RIR databaseAPNIC 43 6%low visibility 29
103.230.226.0/24 Valid RIR databaseAPNIC 43 6%low visibility 29
103.230.227.0/24 Valid RIR databaseAPNIC 43 6%low visibility 29
202.66.176.0/24 Valid RIR databaseAPNIC 43 6%low visibility 29
202.66.177.0/24 Valid RIR databaseAPNIC 43 6%low visibility 29
202.66.179.0/24 Valid RIR databaseAPNIC 43 6%low visibility 29
202.66.178.0/24 Valid RIR databaseAPNIC 11 2%low visibility 5

AS-SET

PeeringDB's irr_as_set for AS132566: AS132566:AS-SKYNETBPS. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS132566 isn't in the set, or no route object for AS132566 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS132566 in itNot covered
AS132566:AS-SKYNETBPS APNIC 302790 Yes 0

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 23 are in fix.csv.

  • ROA: none7
  • Route object: RIR7
  • Route object: not announced9
ChangePrefix or setDetailFull-table peers
ROA: none149.5.60.0/22No ROA covers it. Add a ROA for AS132566, maxLength 22.673 of 673
Route object: RIR149.5.60.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none149.5.60.0/23No ROA covers it. Add a ROA for AS132566, maxLength 23.673 of 673
Route object: RIR149.5.60.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none149.5.62.0/23No ROA covers it. Add a ROA for AS132566, maxLength 23.673 of 673
Route object: RIR149.5.62.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none149.5.60.0/24No ROA covers it. Add a ROA for AS132566, maxLength 24.43 of 673
Route object: RIR149.5.60.0/24Route object only in RADB. Add it in the RIR database for the space.43 of 673
ROA: none149.5.61.0/24No ROA covers it. Add a ROA for AS132566, maxLength 24.43 of 673
Route object: RIR149.5.61.0/24Route object only in RADB. Add it in the RIR database for the space.43 of 673
ROA: none149.5.62.0/24No ROA covers it. Add a ROA for AS132566, maxLength 24.43 of 673
Route object: RIR149.5.62.0/24Route object only in RADB. Add it in the RIR database for the space.43 of 673
ROA: none149.5.63.0/24No ROA covers it. Add a ROA for AS132566, maxLength 24.43 of 673
Route object: RIR149.5.63.0/24Route object only in RADB. Add it in the RIR database for the space.43 of 673

Route objects not announced

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

103.171.114.0/23APNICValid
103.171.114.0/24APNICValid
103.171.115.0/24APNICValid
2406:7340:abc::/48APNICValid
2406:7340:1127::/48APNICValid
2406:7340:ffa3::/48APNICValid
2406:7340:ffa7::/48APNICValid
2406:7340:ffa8::/48APNICValid
2406:7340:ffa9::/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.