Network · data from 2026-11-12
AS39326 Syntura Group Limited
Registry name: HSO-GROUP Syntura Group Limited, GB · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS39326, 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.
| 51.149.9.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 51.149.10.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 51.149.11.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 92.119.136.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 151.170.0.0/16 | No ROA | RIR databaseRIPE | 673 100% |
| 194.34.204.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 194.34.206.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 194.34.207.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 194.34.213.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 2a03:94c0::/40 | No ROA | RIR databaseRIPE | 635 100% |
| 2a09:b540::/29 | No ROA | RIR databaseRIPE | 554 87% |
| 194.0.79.0/24 | Valid | Nonecovered by 194.0.78.0/23 | 673 100% |
| 2a01:348:fab::/48 | Valid | Nonecovered by 2a01:348::/32 | 438 69% |
| 37.46.200.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 46.17.56.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 77.75.104.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 80.71.0.0/19 | Valid | RIR databaseRIPE | 673 100% |
| 89.248.16.0/20 | Valid | RIR databaseRIPE | 673 100% |
| 93.89.80.0/20 | Valid | RIR databaseRIPE | 673 100% |
| 151.236.19.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.51.172.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 185.75.28.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 188.190.5.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 192.121.112.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 192.121.113.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 194.0.77.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 194.0.78.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 195.90.120.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 195.90.121.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 195.238.232.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 217.196.224.0/19 | Valid | RIR databaseRIPE | 673 100% |
| 37.235.54.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 37.235.55.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 2001:a08::/32 | Valid | RIR databaseRIPE | 635 100% |
| 2a01:348::/32 | Valid | RIR databaseRIPE | 635 100% |
AS-SET
PeeringDB's irr_as_set for AS39326: RIPE::AS-GOSCOMB. 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 (AS39326 isn't in the set, or no route object for AS39326 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.
| Name | Database | ASNs | Sets | AS39326 in it | Not covered |
|---|---|---|---|---|---|
| RIPE::AS-GOSCOMB | RIPElists itself further down25 member sets in no database: AS-17290:AS-AUSTIN-HADLEY, AS-202076-OUT, AS-COREINTERNET-ANYCAST, AS-DYFEDIT, AS-ESGOB … | 680 | 191 | 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 54 are in fix.csv.
- ROA: none11
- Route object: none2
- AS-SET: missing member25
- Route object: not announced16
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 51.149.9.0/24 | No ROA covers it. Add a ROA for AS39326, maxLength 24. |
| ROA: none | 51.149.10.0/24 | No ROA covers it. Add a ROA for AS39326, maxLength 24. |
| ROA: none | 51.149.11.0/24 | No ROA covers it. Add a ROA for AS39326, maxLength 24. |
| ROA: none | 92.119.136.0/22 | No ROA covers it. Add a ROA for AS39326, maxLength 22. |
| ROA: none | 151.170.0.0/16 | No ROA covers it. Add a ROA for AS39326, maxLength 16. |
| ROA: none | 194.34.204.0/24 | No ROA covers it. Add a ROA for AS39326, maxLength 24. |
| ROA: none | 194.34.206.0/24 | No ROA covers it. Add a ROA for AS39326, maxLength 24. |
| ROA: none | 194.34.207.0/24 | No ROA covers it. Add a ROA for AS39326, maxLength 24. |
| ROA: none | 194.34.213.0/24 | No ROA covers it. Add a ROA for AS39326, maxLength 24. |
| ROA: none | 2a03:94c0::/40 | No ROA covers it. Add a ROA for AS39326, maxLength 40. |
| ROA: none | 2a09:b540::/29 | No ROA covers it. Add a ROA for AS39326, maxLength 29. |
| Route object: none | 194.0.79.0/24 | No route object for it. A route object for 194.0.78.0/23 with origin AS39326 covers it (filters allowing more-specifics accept it). Add a route object with origin AS39326 in the RIR database for the space. |
| Route object: none | 2a01:348:fab::/48 | No route object for it. A route object for 2a01:348::/32 with origin AS39326 covers it (filters allowing more-specifics accept it). Add a route object with origin AS39326 in the RIR database for the space. |
| AS-SET: missing member | RIPE::AS-GOSCOMB | AS-GOSCOMB (RIPE) lists AS-17290:AS-AUSTIN-HADLEY; no IRR database read has it. |
| AS-SET: missing member | RIPE::AS-GOSCOMB | AS-GOSCOMB (RIPE) lists AS-202076-OUT; no IRR database read has it. |
| AS-SET: missing member | RIPE::AS-GOSCOMB | AS-GOSCOMB (RIPE) lists AS-COREINTERNET-ANYCAST; no IRR database read has it. |
| AS-SET: missing member | RIPE::AS-GOSCOMB | AS-GOSCOMB (RIPE) lists AS-DYFEDIT; no IRR database read has it. |
| AS-SET: missing member | RIPE::AS-GOSCOMB | AS-GOSCOMB (RIPE) lists AS-ESGOB; no IRR database read has it. |
| AS-SET: missing member | RIPE::AS-GOSCOMB | AS-GOSCOMB (RIPE) lists AS-HAMLESH; no IRR database read has it. |
| AS-SET: missing member | RIPE::AS-GOSCOMB | AS-GOSCOMB (RIPE) lists AS-HSC; no IRR database read has it. |
| AS-SET: missing member | RIPE::AS-GOSCOMB | AS-GOSCOMB (RIPE) lists AS-HYEHOST; no IRR database read has it. |
| AS-SET: missing member | RIPE::AS-GOSCOMB | AS-GOSCOMB (RIPE) lists AS-KEWLIO-OFFSITE; no IRR database read has it. |
| AS-SET: missing member | RIPE::AS-GOSCOMB | AS-GOSCOMB (RIPE) lists AS-NAMECRANE; no IRR database read has it. |
| AS-SET: missing member | RIPE::AS-GOSCOMB | AS-GOSCOMB (RIPE) lists AS-NOMINET-NS; no IRR database read has it. |
| AS-SET: missing member | RIPE::AS-GOSCOMB | AS-GOSCOMB (RIPE) lists AS-NUQE; no IRR database read has it. |
| AS-SET: missing member | RIPE::AS-GOSCOMB | AS-GOSCOMB (RIPE) lists AS-OCCAID; no IRR database read has it. |
| AS-SET: missing member | RIPE::AS-GOSCOMB | AS-GOSCOMB (RIPE) lists AS-ONECOMANYCAST; no IRR database read has it. |
| AS-SET: missing member | RIPE::AS-GOSCOMB | AS-GOSCOMB (RIPE) lists AS-PBB; no IRR database read has it. |
| AS-SET: missing member | RIPE::AS-GOSCOMB | AS-GOSCOMB (RIPE) lists AS-QN-ANYCAST; no IRR database read has it. |
| AS-SET: missing member | RIPE::AS-GOSCOMB | AS-GOSCOMB (RIPE) lists AS-QP; no IRR database read has it. |
| AS-SET: missing member | RIPE::AS-GOSCOMB | AS-GOSCOMB (RIPE) lists AS-SERV; no IRR database read has it. |
| AS-SET: missing member | RIPE::AS-GOSCOMB | AS-GOSCOMB (RIPE) lists AS-STEFAN; no IRR database read has it. |
| AS-SET: missing member | RIPE::AS-GOSCOMB | AS-GOSCOMB (RIPE) lists AS-SYNERGYWORKS; no IRR database read has it. |
| AS-SET: missing member | RIPE::AS-GOSCOMB | AS-GOSCOMB (RIPE) lists AS152135:AS-CSSI; no IRR database read has it. |
| AS-SET: missing member | RIPE::AS-GOSCOMB | AS-GOSCOMB (RIPE) lists AS199746:AS-NEXTSERV; no IRR database read has it. |
| AS-SET: missing member | RIPE::AS-GOSCOMB | AS-GOSCOMB (RIPE) lists AS203105:AS-FLIMPIE; no IRR database read has it. |
| AS-SET: missing member | RIPE::AS-GOSCOMB | AS-GOSCOMB (RIPE) lists AS206754:AS-TRANSIT; no IRR database read has it. |
| AS-SET: missing member | RIPE::AS-GOSCOMB | AS-GOSCOMB (RIPE) lists AS400719:AS-ALL; no IRR database read has it. |
Route objects not announced
Route objects with origin AS39326 whose prefix no peer sees AS39326 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 91.208.242.0/24 | RIPE | No ROA |
| 185.235.98.0/24 | RIPE | Invalid: origin |
| 192.88.99.0/24 | RIPE-NONAUTH | No ROA |
| 193.151.124.0/24 | RIPE | Valid |
| 194.0.76.0/24 | RIPE | No ROA |
| 194.34.205.0/24 | RIPE | No ROA |
| 194.34.208.0/24 | RIPE | No ROA |
| 194.34.209.0/24 | RIPE | No ROA |
| 199.74.220.0/24 | ALTDB | No ROA |
| 2001:1868:53::/48 | ALTDB | Invalid: origin |
| 2002::/16 | RIPE-NONAUTH | No ROA |
| 2a00:dd80:3a::/48 | RIPE | Invalid: origin |
| 2a00:dd80:3c::/48 | RIPE | Invalid: origin |
| 2a00:dd80:3e::/48 | RIPE | Invalid: origin |
| 2a03:f80:44::/48 | RIPE | Valid |
| 2a03:f80:441::/48 | RIPE | Valid |
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.