Network · data from 2026-11-12
AS205380 GEEKTEAMLLLC GeekTeam L.L.C-FZ
Registry name: GEEKTEAMLLLC GeekTeam L.L.C-FZ, AE · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS205380, 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.
| 104.238.26.0/24 | Valid | Other origin only | 673 100% |
| 45.8.23.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 151.242.206.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
AS-SET
AS205380 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 3 are in fix.csv.
- Route object: none1
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 104.238.26.0/24 | Route objects for it name AS49981. Add a route object with origin AS205380 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS205380 whose prefix no peer sees AS205380 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 154.222.133.0/24 | AFRINIC | Invalid: origin |
| 2a0c:b641:6a0::/44 | 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.