Network · data from 2026-11-12

AS269394 Mitas - Internet Banda Larga

Registry name: AS269394 - Mitas - Internet Banda Larga Ltda, BR · PeeringDB

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

1IPv6 routes 100.0% RPKI valid · 100.0% with a route object

0RPKI invalid 0 origin · 0 maxLength

0No ROA 0 with no route object for this origin

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

0Route objects not announced registered with origin AS269394, seen from no peer

Announced routes

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


45.185.216.0/22	Valid	Other IRR onlyRADB, TC	672 100%	67
45.185.217.0/24	Valid	Other IRR onlyRADB, TC	672 100%	67
45.185.218.0/24	Valid	Other IRR onlyRADB, TC	672 100%	67
138.36.8.0/22	Valid	Other IRR onlyRADB	672 100%	67
138.36.8.0/24	Valid	Other IRR onlyTC	672 100%	67
138.36.9.0/24	Valid	Other IRR onlyTC	672 100%	67
138.36.10.0/24	Valid	Other IRR onlyTC	672 100%	67
45.185.216.0/24	Valid	Other IRR onlyRADB, TC	671 100%	67
45.185.219.0/24	Valid	Other IRR onlyRADB, TC	671 100%	67
138.36.11.0/24	Valid	Other IRR onlyTC	671 100%	67
2804:63f4::/32	Valid	Other IRR onlyRADB, TC	636 100%	67

AS-SET

PeeringDB's irr_as_set for AS269394: AS-269394. 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 (AS269394 isn't in the set, or no route object for AS269394 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	AS269394 in it	Not covered
AS-269394	In no IRR database read today.

Name

Database

ASNs

Sets

Route objects

AS269394 in it

Not covered

AS-269394

In no IRR database read today.

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 12 are in fix.csv.

Route object: RIR11
AS-SET: not found1

Change	Prefix or set	Detail	Full-table peers
Route object: RIR	45.185.216.0/22	Route object only in RADB, TC. Add it in the RIR database for the space.	672 of 673
Route object: RIR	45.185.217.0/24	Route object only in RADB, TC. Add it in the RIR database for the space.	672 of 673
Route object: RIR	45.185.218.0/24	Route object only in RADB, TC. Add it in the RIR database for the space.	672 of 673
Route object: RIR	138.36.8.0/22	Route object only in RADB. Add it in the RIR database for the space.	672 of 673
Route object: RIR	138.36.8.0/24	Route object only in TC. Add it in the RIR database for the space.	672 of 673
Route object: RIR	138.36.9.0/24	Route object only in TC. Add it in the RIR database for the space.	672 of 673
Route object: RIR	138.36.10.0/24	Route object only in TC. Add it in the RIR database for the space.	672 of 673
Route object: RIR	45.185.216.0/24	Route object only in RADB, TC. Add it in the RIR database for the space.	671 of 673
Route object: RIR	45.185.219.0/24	Route object only in RADB, TC. Add it in the RIR database for the space.	671 of 673
Route object: RIR	138.36.11.0/24	Route object only in TC. Add it in the RIR database for the space.	671 of 673
Route object: RIR	2804:63f4::/32	Route object only in RADB, TC. Add it in the RIR database for the space.	636 of 636
AS-SET: not found	AS-269394	PeeringDB names AS-269394; no IRR database read has it.

Change

Prefix or set

Detail

Full-table peers

Route object: RIR

45.185.216.0/22

Route object only in RADB, TC. Add it in the RIR database for the space.

672 of 673

Route object: RIR

45.185.217.0/24

Route object only in RADB, TC. Add it in the RIR database for the space.

672 of 673

Route object: RIR

45.185.218.0/24

Route object only in RADB, TC. Add it in the RIR database for the space.

672 of 673

Route object: RIR

138.36.8.0/22

Route object only in RADB. Add it in the RIR database for the space.

672 of 673

Route object: RIR

138.36.8.0/24

Route object only in TC. Add it in the RIR database for the space.

672 of 673

Route object: RIR

138.36.9.0/24

Route object only in TC. Add it in the RIR database for the space.

672 of 673

Route object: RIR

138.36.10.0/24

Route object only in TC. Add it in the RIR database for the space.

672 of 673

Route object: RIR

45.185.216.0/24

Route object only in RADB, TC. Add it in the RIR database for the space.

671 of 673

Route object: RIR

45.185.219.0/24

Route object only in RADB, TC. Add it in the RIR database for the space.

671 of 673

Route object: RIR

138.36.11.0/24

Route object only in TC. Add it in the RIR database for the space.

671 of 673

Route object: RIR

2804:63f4::/32

Route object only in RADB, TC. Add it in the RIR database for the space.

636 of 636

AS-SET: not found

AS-269394

PeeringDB names AS-269394; no IRR database read has it.

Route objects not announced

Every route object with origin AS269394 is announced.

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.