Network · data from 2026-11-12
AS203861 ServerExpress
Registry name: SERVEREXPRESS-AS Miteflux Technologies Ltd, GB · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS203861, 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.
| 2a14:c380:1200::/40 | Invalid: origin | Other origin only | 29 5%low visibility |
| 217.60.78.188/32 | Invalid: origin | Nonecovered by 217.60.76.0/22 | 0 0%low visibility |
| 31.59.160.9/32 | Invalid: maxLength | Nonecovered by 31.59.160.0/24 | 1 0%low visibility |
| 31.59.160.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 217.60.29.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 5.175.215.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 31.58.218.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 217.60.77.0/24 | Valid | RIR databaseRIPE | 667 99% |
| 2a14:c380:1100::/40 | Valid | RIR databaseRIPE | 632 99% |
AS-SET
PeeringDB's irr_as_set for AS203861: AS203861:AS-MITEFLUX. 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 (AS203861 isn't in the set, or no route object for AS203861 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 | AS203861 in it | Not covered |
|---|---|---|---|---|---|
| AS203861:AS-MITEFLUX | RIPE | 6 | 2 | Yes | 3 |
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 9 are in fix.csv.
- ROA: origin2
- ROA: maxLength1
- Route object: none3
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 2a14:c380:1200::/40 | ROAs covering it name AS198189, not AS203861. If AS203861 should announce it, add a ROA for AS203861. |
| Route object: none | 2a14:c380:1200::/40 | Route objects for it name AS198189. Add a route object with origin AS203861 in the RIR database for the space. |
| ROA: origin | 217.60.78.188/32 | ROAs covering it name AS198189, not AS203861. If AS203861 should announce it, add a ROA for AS203861. |
| Route object: none | 217.60.78.188/32 | No route object for it. A route object for 217.60.76.0/22 with origin AS203861 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS203861 in the RIR database for the space. |
| ROA: maxLength | 31.59.160.9/32 | ROA 31.59.160.0/24 AS203861 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 31.59.160.9/32. |
| Route object: none | 31.59.160.9/32 | No route object for it. A route object for 31.59.160.0/24 with origin AS203861 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS203861 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS203861 whose prefix no peer sees AS203861 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 65.64.2.0/24 | ALTDB | No ROA |
| 67.67.246.0/24 | ALTDB | No ROA |
| 217.60.76.0/22 | RADB | No ROA |
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.