Network · data from 2026-11-12
AS60168 NETSERVICEBG Net Service BG Ltd
Registry name: NETSERVICEBG Net Service BG Ltd, BG · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS60168, 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.
| 2a0d:3380::/48 | No ROA | None | 635 100% |
| 2a0d:3380:1::/48 | No ROA | None | 635 100% |
| 5.32.128.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 5.32.130.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 5.32.131.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 62.68.90.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 78.128.93.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 78.128.95.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 79.124.69.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 79.124.70.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 88.80.152.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 88.80.156.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 88.80.158.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 151.237.136.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 194.8.53.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 5.32.129.0/24 | Valid | RIR databaseRIPE | 2 0%low visibility |
AS-SET
AS60168 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 21 are in fix.csv.
- ROA: none2
- Route object: none2
- Route object: not announced17
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2a0d:3380::/48 | No ROA covers it. Add a ROA for AS60168, maxLength 48. |
| Route object: none | 2a0d:3380::/48 | No route object for it. Add a route object with origin AS60168 in the RIR database for the space. |
| ROA: none | 2a0d:3380:1::/48 | No ROA covers it. Add a ROA for AS60168, maxLength 48. |
| Route object: none | 2a0d:3380:1::/48 | No route object for it. Add a route object with origin AS60168 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS60168 whose prefix no peer sees AS60168 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 5.32.128.0/22 | RIPE | No ROA |
| 5.32.128.0/23 | RIPE | No ROA |
| 5.32.130.0/23 | RIPE | No ROA |
| 79.124.68.0/22 | RIPE | Valid |
| 79.124.68.0/23 | RIPE | Valid |
| 79.124.68.0/24 | RIPE | Valid |
| 79.124.70.0/23 | RIPE | Valid |
| 79.124.71.0/24 | RIPE | Valid |
| 88.80.156.0/22 | RIPE | Valid |
| 151.237.136.0/24 | RIPE | Invalid: maxLength |
| 151.237.137.0/24 | RIPE | Invalid: maxLength |
| 185.243.248.0/24 | RIPE | No ROA |
| 185.243.249.0/24 | RIPE | No ROA |
| 185.243.250.0/24 | RIPE | No ROA |
| 185.243.251.0/24 | RIPE | No ROA |
| 195.177.218.0/24 | RIPE | Valid |
| 195.177.219.0/24 | 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.