Network · data from 2026-11-12
AS210356 BattleHost KAUA REIS DA SILVA trading as BattleHost
Registry name: BattleHost KAUA REIS DA SILVA trading as BattleHost, BR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS210356, 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.
| 37.148.133.115/32 | Invalid: maxLength | Nonecovered by 37.148.132.0/22 | 0 0%low visibility |
| 37.148.135.134/32 | Invalid: maxLength | Nonecovered by 37.148.132.0/22 | 0 0%low visibility |
| 37.148.132.0/23 | Valid | Nonecovered by 37.148.132.0/22 | 7 1%low visibility |
| 37.148.134.0/23 | Valid | Nonecovered by 37.148.132.0/22 | 7 1%low visibility |
| 181.214.48.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 37.148.132.0/22 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 108.165.179.0/24 | Valid | RIR databaseARIN, RADB | 672 100% |
| 108.165.230.0/24 | Valid | RIR databaseARIN, RADB | 672 100% |
| 181.214.221.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 144.225.189.0/24 | Valid | RIR databaseARIN, RADB | 671 100% |
| 167.148.161.0/24 | Valid | RIR databaseRADB, RIPE | 671 100% |
| 2a0c:b641:600::/44 | Valid | RIR databaseRADB, RIPE | 636 100% |
AS-SET
AS210356 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 8 are in fix.csv.
- ROA: maxLength2
- Route object: none4
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: maxLength | 37.148.133.115/32 | ROA 37.148.132.0/22 AS210356 has maxLength 22; ROA 37.148.132.0/23 AS210356 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 37.148.133.115/32. |
| Route object: none | 37.148.133.115/32 | No route object for it. A route object for 37.148.132.0/22 with origin AS210356 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS210356 in the RIR database for the space. |
| ROA: maxLength | 37.148.135.134/32 | ROA 37.148.132.0/22 AS210356 has maxLength 22; ROA 37.148.134.0/23 AS210356 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 37.148.135.134/32. |
| Route object: none | 37.148.135.134/32 | No route object for it. A route object for 37.148.132.0/22 with origin AS210356 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS210356 in the RIR database for the space. |
| Route object: none | 37.148.132.0/23 | No route object for it. A route object for 37.148.132.0/22 with origin AS210356 covers it (filters allowing more-specifics accept it). Add a route object with origin AS210356 in the RIR database for the space. |
| Route object: none | 37.148.134.0/23 | No route object for it. A route object for 37.148.132.0/22 with origin AS210356 covers it (filters allowing more-specifics accept it). Add a route object with origin AS210356 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS210356 whose prefix no peer sees AS210356 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 188.220.168.0/21 | RADB, RIPE | Valid |
| 2a13:9500:141::/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.