bgpreport

Network · data from 2026-11-12

AS213738 HOSTEG

Registry name: HOSTEG HOSTEG HOSPEDAGEM E SERVIDORES LTDA, BR · PeeringDB

8IPv4 routes 75.0% RPKI valid · 25.0% with a route object
1IPv6 routes 100.0% RPKI valid · 100.0% with a route object
2RPKI invalid 2 origin · 0 maxLength
0No ROA 6 with no route object for this origin
2Low visibility seen by under 10% of full-table peers
3Route objects not announced registered with origin AS213738, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS213738, 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.
181.214.95.0/24 Invalid: origin Other origin only 2 0%low visibility 2
102.216.82.0/24 Invalid: origin Other origin only 1 0%low visibility 1
162.141.108.0/24 Valid Nonecovered by 162.141.108.0/23 669 99% 67
74.1.20.0/24 Valid Nonecovered by 74.1.20.0/23 668 99% 67
74.1.21.0/24 Valid Nonecovered by 74.1.20.0/23 668 99% 67
162.141.109.0/24 Valid Nonecovered by 162.141.108.0/23 668 99% 67
74.1.20.0/23 Valid RIR databaseARIN, RADB 669 99% 67
162.141.108.0/23 Valid RIR databaseRADB, RIPE 669 99% 67
2a13:9500:fd::/48 Valid RIR databaseRIPE 634 100% 69

AS-SET

AS213738's PeeringDB record names no 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 11 are in fix.csv.

  • ROA: origin2
  • Route object: none6
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: origin181.214.95.0/24ROAs covering it name AS218535, not AS213738. If AS213738 should announce it, add a ROA for AS213738.2 of 673
Route object: none181.214.95.0/24Route objects for it name AS218535. Add a route object with origin AS213738 in the RIR database for the space.2 of 673
ROA: origin102.216.82.0/24ROAs covering it name AS211575, not AS213738. If AS213738 should announce it, add a ROA for AS213738.1 of 673
Route object: none102.216.82.0/24Route objects for it name AS211575, AS328992. Add a route object with origin AS213738 in the RIR database for the space.1 of 673
Route object: none162.141.108.0/24No route object for it. A route object for 162.141.108.0/23 with origin AS213738 covers it (filters allowing more-specifics accept it). Add a route object with origin AS213738 in the RIR database for the space.669 of 673
Route object: none74.1.20.0/24No route object for it. A route object for 74.1.20.0/23 with origin AS213738 covers it (filters allowing more-specifics accept it). Add a route object with origin AS213738 in the RIR database for the space.668 of 673
Route object: none74.1.21.0/24No route object for it. A route object for 74.1.20.0/23 with origin AS213738 covers it (filters allowing more-specifics accept it). Add a route object with origin AS213738 in the RIR database for the space.668 of 673
Route object: none162.141.109.0/24No route object for it. A route object for 162.141.108.0/23 with origin AS213738 covers it (filters allowing more-specifics accept it). Add a route object with origin AS213738 in the RIR database for the space.668 of 673

Route objects not announced

Route objects with origin AS213738 whose prefix no peer sees AS213738 announce. Many are kept on purpose (backup routes, space announced only in some places).

a0c:b641:70::/44RADBNo ROA
2a0c:b641:70::/44RIPEValid
2a0c:b641:71::/48RADBValid

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.