bgpreport

Network · data from 2026-11-12

AS58325 Hydra Communications Ltd (ASIA)

Registry name: BANDWIDTH-ASIA Hydra Communications Ltd, GB · PeeringDB

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

Announced routes

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

64.204.144.0/22 Invalid: origin Other origin only 1 0%low visibility 1
212.135.136.0/23 Invalid: origin RIR databaseRIPE 1 0%low visibility 1
212.135.140.0/23 Invalid: origin RIR databaseRIPE 1 0%low visibility 1
212.135.142.0/23 Invalid: origin RIR databaseRIPE 1 0%low visibility 1
212.135.144.0/23 Invalid: origin RIR databaseRIPE 1 0%low visibility 1
195.178.148.0/23 No ROA Other origin only 3 0%low visibility 3
133.157.0.0/22 Valid Other IRR onlyJPIRR 671 100% 67
133.157.4.0/22 Valid Other IRR onlyJPIRR 671 100% 67
133.157.24.0/22 Valid Other IRR onlyJPIRR 671 100% 67
133.157.28.0/22 Valid Other IRR onlyJPIRR 671 100% 67
64.204.92.0/22 Valid RIR databaseARIN, RADB 671 100% 67
69.5.174.0/24 Valid RIR databaseRIPE 671 100% 67
86.109.88.0/22 Valid RIR databaseRADB, RIPE 671 100% 67
89.32.161.0/24 Valid RIR databaseRIPE 671 100% 67
93.118.40.0/22 Valid RIR databaseRIPE 671 100% 67
94.177.17.0/24 Valid RIR databaseRIPE 671 100% 67
94.192.56.0/22 Valid RIR databaseRADB, RIPE 671 100% 67
94.192.60.0/22 Valid RIR databaseRADB, RIPE 671 100% 67
160.21.76.0/22 Valid RIR databaseRADB, RIPE 671 100% 67
212.68.172.0/22 Valid RIR databaseRIPE 671 100% 67
212.68.184.0/22 Valid RIR databaseRIPE 671 100% 67
212.134.220.0/22 Valid RIR databaseRADB, RIPE 671 100% 67
212.135.130.0/23 Valid RIR databaseRADB, RIPE 671 100% 67
212.135.132.0/23 Valid RIR databaseRADB, RIPE 671 100% 67
46.231.167.0/24 Valid RIR databaseRIPE 670 100% 67
109.64.200.0/24 Valid RIR databaseRADB, RIPE 670 100% 67
188.221.231.0/24 Valid RIR databaseRADB, RIPE 670 100% 67
2a01:4020:40::/44 Valid RIR databaseRIPE 632 99% 67

AS-SET

PeeringDB's irr_as_set for AS58325: AS58325:AS-ALL. 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 (AS58325 isn't in the set, or no route object for AS58325 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 objectsAS58325 in itNot covered
AS58325:AS-ALL RIPE 51327 Yes 2

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

  • ROA: origin5
  • ROA: none1
  • Route object: none2
  • Route object: RIR4
  • Route object: not announced19
ChangePrefix or setDetailFull-table peers
ROA: origin64.204.144.0/22ROAs covering it name AS834, not AS58325. If AS58325 should announce it, add a ROA for AS58325.1 of 673
Route object: none64.204.144.0/22Route objects for it name AS834. Add a route object with origin AS58325 in the RIR database for the space.1 of 673
ROA: origin212.135.136.0/23ROAs covering it name AS834, not AS58325. If AS58325 should announce it, add a ROA for AS58325.1 of 673
ROA: origin212.135.140.0/23ROAs covering it name AS834, not AS58325. If AS58325 should announce it, add a ROA for AS58325.1 of 673
ROA: origin212.135.142.0/23ROAs covering it name AS834, not AS58325. If AS58325 should announce it, add a ROA for AS58325.1 of 673
ROA: origin212.135.144.0/23ROAs covering it name AS834, not AS58325. If AS58325 should announce it, add a ROA for AS58325.1 of 673
ROA: none195.178.148.0/23No ROA covers it. Add a ROA for AS58325, maxLength 23.3 of 673
Route object: none195.178.148.0/23Route objects for it name AS34450. Add a route object with origin AS58325 in the RIR database for the space.3 of 673
Route object: RIR133.157.0.0/22Route object only in JPIRR. Add it in the RIR database for the space.671 of 673
Route object: RIR133.157.4.0/22Route object only in JPIRR. Add it in the RIR database for the space.671 of 673
Route object: RIR133.157.24.0/22Route object only in JPIRR. Add it in the RIR database for the space.671 of 673
Route object: RIR133.157.28.0/22Route object only in JPIRR. Add it in the RIR database for the space.671 of 673

Route objects not announced

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

69.5.172.0/24RIPEValid
77.216.13.0/24RADB, RIPEValid
93.118.40.0/23RIPEValid
93.118.40.0/24RIPEValid
93.118.41.0/24RIPEValid
93.118.42.0/23RIPEValid
93.118.42.0/24RIPEValid
93.118.43.0/24RIPEValid
103.172.134.0/24APNICValid
103.172.135.0/24APNICValid
133.157.8.0/22JPIRRInvalid: origin
133.157.12.0/22JPIRRInvalid: origin
133.157.16.0/22JPIRRInvalid: origin
133.157.20.0/22JPIRRInvalid: origin
212.134.236.0/22RIPEInvalid: origin
212.134.244.0/22RIPEInvalid: origin
212.134.252.0/22RIPEInvalid: origin
212.135.138.0/23RIPENo ROA
212.135.146.0/23RADB, RIPEValid

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.