Network · data from 2026-11-12
AS202260 GABRIEL-AS
Registry name: GABRIEL-AS GAMESHIELD HOSTING SOLUTIONS S.R.L, RO · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS202260, 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.
| 155.117.166.0/24 | Invalid: origin | Other origin only | 32 5%low visibility |
| 2a10:fa81:1a06::/48 | Invalid: origin | None | 1 0%low visibility |
| 2a0b:4e07:b31::/48 | Valid | RIR databaseRIPE | 633 100% |
AS-SET
PeeringDB's irr_as_set for AS202260: AS202260. 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 (AS202260 isn't in the set, or no route object for AS202260 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 | AS202260 in it | Not covered | |
|---|---|---|---|---|---|---|
| AS202260 | A single AS number, not a set: AS202260 (this network), 3 route objects. | |||||
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 6 are in fix.csv.
- ROA: origin2
- Route object: none2
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 155.117.166.0/24 | ROAs covering it name AS214483, not AS202260. If AS202260 should announce it, add a ROA for AS202260. |
| Route object: none | 155.117.166.0/24 | Route objects for it name AS214483. Add a route object with origin AS202260 in the RIR database for the space. |
| ROA: origin | 2a10:fa81:1a06::/48 | ROAs covering it name AS63023, not AS202260. If AS202260 should announce it, add a ROA for AS202260. |
| Route object: none | 2a10:fa81:1a06::/48 | No route object for it. Add a route object with origin AS202260 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS202260 whose prefix no peer sees AS202260 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2a06:a005:1d00::/44 | RADB | No ROA |
| 2a13:9500:1b1::/48 | 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.