Network · data from 2026-11-12
AS204997 FIRSTBYTE-AS FIRST SERVER LIMITED
Registry name: FIRSTBYTE-AS FIRST SERVER LIMITED, GB · not in PeeringDB
65IPv4 routes
100.0% RPKI valid · 100.0% with a route object
16IPv6 routes
93.8% RPKI valid · 100.0% with a route object
1RPKI invalid
1 origin · 0 maxLength
0No ROA
0 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
16Route objects not announced
registered with origin AS204997, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS204997, 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.
| 2a00:e462:ffff::/48 | Invalid: origin | RIR databaseRIPE | 94 15% |
| 45.144.64.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 45.144.65.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 45.144.66.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 45.144.67.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 46.17.104.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 91.217.81.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 104.128.132.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 104.128.136.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 104.128.137.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 104.128.140.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 104.128.141.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 135.136.180.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 135.136.188.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 135.136.191.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 139.28.222.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 139.28.223.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 147.78.64.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 147.78.65.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 147.78.66.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 147.78.67.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 157.228.134.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 157.228.135.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 157.228.136.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 157.228.137.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 157.228.190.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 178.253.38.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 178.253.39.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 178.253.44.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 178.253.45.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 185.17.0.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 185.17.3.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 185.139.68.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 185.139.69.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 185.139.70.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 185.139.71.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 185.174.138.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 185.180.231.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 185.188.182.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 185.188.183.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 185.195.24.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 185.195.25.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 185.195.26.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 185.195.27.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 185.204.0.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 185.204.2.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 185.204.3.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 185.212.148.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 185.244.172.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 185.244.173.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 185.252.146.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 185.252.147.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 185.255.132.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 185.255.133.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 185.255.134.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 185.255.135.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 193.109.78.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 193.109.79.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 195.66.114.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 185.104.248.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 185.104.249.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 185.189.12.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 185.189.13.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 185.189.14.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 185.189.15.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 185.180.230.0/24 | Valid | RIR databaseRIPE | 650 97% |
| 2a04:5200:fb01::/48 | Valid | RIR databaseRIPE | 636 100% |
| 2a04:5200:fb02::/48 | Valid | RIR databaseRIPE | 636 100% |
| 2a04:5200:ff00::/48 | Valid | RIR databaseRIPE | 636 100% |
| 2a04:5200:ff10::/48 | Valid | RIR databaseRIPE | 636 100% |
| 2a04:5200:fff1::/48 | Valid | RIR databaseRIPE | 636 100% |
| 2a04:5200:fff2::/48 | Valid | RIR databaseRIPE | 636 100% |
| 2a04:5200:fff3::/48 | Valid | RIR databaseRIPE | 636 100% |
| 2a04:5200:fff4::/48 | Valid | RIR databaseRIPE | 636 100% |
| 2a04:5200:fff5::/48 | Valid | RIR databaseRIPE | 636 100% |
| 2a04:5200:fff6::/48 | Valid | RIR databaseRIPE | 636 100% |
| 2a04:5200:fff7::/48 | Valid | RIR databaseRIPE | 636 100% |
| 2a04:5200:fff8::/48 | Valid | RIR databaseRIPE | 636 100% |
| 2a04:5200:fff9::/48 | Valid | RIR databaseRIPE | 636 100% |
| 2a04:5200:ffff::/48 | Valid | RIR databaseRIPE | 636 100% |
| 2a0c:5d00:3001::/48 | Valid | RIR databaseRIPE | 636 100% |
AS-SET
AS204997 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 17 are in fix.csv.
- ROA: origin1
- Route object: not announced16
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 2a00:e462:ffff::/48 | ROAs covering it name AS23532, AS55201, AS139803, AS197537, AS202736, AS204936, AS204968, AS213507, AS216138, AS400342, AS401163, not AS204997. If AS204997 should announce it, add a ROA for AS204997. |
Route objects not announced
Route objects with origin AS204997 whose prefix no peer sees AS204997 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 46.17.105.0/24 | RIPE | Invalid: origin |
| 91.217.76.0/24 | RIPE | Invalid: origin |
| 185.40.4.0/24 | RIPE | Valid |
| 185.200.191.0/24 | RIPE | Invalid: origin |
| 2a04:5200:68::/48 | RIPE | Invalid: origin |
| 2a04:5201::/32 | RIPE | No ROA |
| 2a04:5201:2::/48 | RIPE | Invalid: origin |
| 2a04:5201:3::/48 | RIPE | No ROA |
| 2a04:5202::/32 | RIPE | Invalid: origin |
| 2a09:5302::/48 | RIPE | Invalid: origin |
| 2a0c:5d00:ff03::/48 | RIPE | Valid |
| 2a0c:5d05:ffff::/48 | RIPE | No ROA |
| 2a0c:aa40::/32 | RIPE | Invalid: origin |
| 2a0c:aa41::/32 | RIPE | Invalid: origin |
| 2a0c:aa42::/32 | RIPE | Invalid: origin |
| 2a0c:aa43::/32 | RIPE | Invalid: origin |
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.