Network · data from 2026-11-12

AS267355 HOSTIDC INTERNET DATACENTER

Registry name: AS267355 - HOSTIDC INTERNET DATACENTER LTDA, BR · PeeringDB

4IPv4 routes 100.0% RPKI valid · 100.0% with a route object

2IPv6 routes 100.0% RPKI valid · 50.0% with a route object

0RPKI invalid 0 origin · 0 maxLength

0No ROA 1 with no route object for this origin

0Low visibility seen by under 10% of full-table peers

4Route objects not announced registered with origin AS267355, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS267355, 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.


2804:4c30:c000::/34	Valid	Nonecovered by 2804:4c30:8000::/33	631 99%	67
45.234.93.0/24	Valid	Other IRR onlyRADB	668 99%	67
45.234.95.0/24	Valid	Other IRR onlyRADB	668 99%	67
45.234.92.0/24	Valid	Other IRR onlyRADB	666 99%	67
45.234.94.0/24	Valid	Other IRR onlyRADB	665 99%	67
2804:4c30:8000::/33	Valid	Other IRR onlyRADB	635 100%	67

AS-SET

PeeringDB's irr_as_set for AS267355: AS267355. 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 (AS267355 isn't in the set, or no route object for AS267355 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	Route objects	AS267355 in it	Not covered
AS267355	A single AS number, not a set: AS267355 (this network), 9 route objects.

Name

Database

ASNs

Sets

Route objects

AS267355 in it

Not covered

AS267355

A single AS number, not a set: AS267355 (this network), 9 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 10 are in fix.csv.

Route object: none1
Route object: RIR5
Route object: not announced4

Change	Prefix or set	Detail	Full-table peers
Route object: none	2804:4c30:c000::/34	No route object for it. A route object for 2804:4c30:8000::/33 with origin AS267355 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267355 in the RIR database for the space.	631 of 636
Route object: RIR	45.234.93.0/24	Route object only in RADB. Add it in the RIR database for the space.	668 of 673
Route object: RIR	45.234.95.0/24	Route object only in RADB. Add it in the RIR database for the space.	668 of 673
Route object: RIR	45.234.92.0/24	Route object only in RADB. Add it in the RIR database for the space.	666 of 673
Route object: RIR	45.234.94.0/24	Route object only in RADB. Add it in the RIR database for the space.	665 of 673
Route object: RIR	2804:4c30:8000::/33	Route object only in RADB. Add it in the RIR database for the space.	635 of 636

Change

Prefix or set

Detail

Full-table peers

Route object: none

2804:4c30:c000::/34

No route object for it. A route object for 2804:4c30:8000::/33 with origin AS267355 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267355 in the RIR database for the space.

631 of 636

Route object: RIR

45.234.93.0/24