Network · data from 2026-11-12
AS49870 Alsycon AS49870
Registry name: AS49870-BV Alsycon B.V., NL · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS49870, 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.
| 160.119.66.206/32 | No ROA | Nonecovered by 160.119.64.0/22 | 1 0%low visibility |
| 160.119.64.0/22 | No ROA | Other IRR onlyRADB | 673 100% |
| 160.119.69.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 160.119.71.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 160.119.74.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 160.119.75.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 160.119.76.0/23 | No ROA | Other IRR onlyRADB | 673 100% |
| 160.119.78.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 196.61.64.0/22 | No ROA | Other IRR onlyRADB | 673 100% |
| 2.56.167.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 45.80.36.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 45.81.22.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 45.95.144.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 45.140.222.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 89.190.159.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 169.239.130.0/24 | Valid | RIR databaseAFRINIC | 673 100% |
| 212.107.12.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 45.95.146.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 45.95.147.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 194.50.16.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 185.224.128.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 77.83.240.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 89.190.156.0/24 | Valid | RIR databaseRIPE | 666 99% |
| 2a0e:3980::/29 | Valid | RIR databaseRIPE | 635 100% |
| 89.116.202.0/24 | Valid | RIR databaseRADB, RIPE | 108 16% |
AS-SET
PeeringDB's irr_as_set for AS49870: AS-49870. 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 (AS49870 isn't in the set, or no route object for AS49870 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 | AS49870 in it | Not covered |
|---|---|---|---|---|---|
| AS-49870 | RIPE | 111 | 8 | Yes | 1 |
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 22 are in fix.csv.
- ROA: none9
- Route object: none1
- Route object: RIR8
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 160.119.66.206/32 | No ROA covers it. Add a ROA for AS49870, maxLength 32. |
| Route object: none | 160.119.66.206/32 | No route object for it. A route object for 160.119.64.0/22 with origin AS49870 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS49870 in the RIR database for the space. |
| ROA: none | 160.119.64.0/22 | No ROA covers it. Add a ROA for AS49870, maxLength 22. |
| Route object: RIR | 160.119.64.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 160.119.69.0/24 | No ROA covers it. Add a ROA for AS49870, maxLength 24. |
| Route object: RIR | 160.119.69.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 160.119.71.0/24 | No ROA covers it. Add a ROA for AS49870, maxLength 24. |
| Route object: RIR | 160.119.71.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 160.119.74.0/24 | No ROA covers it. Add a ROA for AS49870, maxLength 24. |
| Route object: RIR | 160.119.74.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 160.119.75.0/24 | No ROA covers it. Add a ROA for AS49870, maxLength 24. |
| Route object: RIR | 160.119.75.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 160.119.76.0/23 | No ROA covers it. Add a ROA for AS49870, maxLength 23. |
| Route object: RIR | 160.119.76.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 160.119.78.0/24 | No ROA covers it. Add a ROA for AS49870, maxLength 24. |
| Route object: RIR | 160.119.78.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 196.61.64.0/22 | No ROA covers it. Add a ROA for AS49870, maxLength 22. |
| Route object: RIR | 196.61.64.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS49870 whose prefix no peer sees AS49870 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 85.11.182.0/24 | RIPE | Invalid: origin |
| 85.11.190.0/24 | RIPE | Invalid: origin |
| 160.119.72.0/23 | RADB | No ROA |
| 194.50.16.0/23 | 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.