Network · data from 2026-11-12

AS269221 VIP CONNECT - SOLUCOES EM COMUNICACAO E NETWORKS

Registry name: AS269221 - VIP CONNECT - SOLUCOES EM COMUNICACAO E NETWORKS, BR · PeeringDB

7IPv4 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

510Route objects not announced registered with origin AS269221, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS269221, 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.181.116.0/22	Valid	Other IRR onlyRADB, TC	671 100%	67
2804:6138::/32	Valid	Other IRR onlyRADB, TC	636 100%	67
45.181.116.0/23	Valid	Other IRR onlyRADB, TC	211 31%	56
45.181.116.0/24	Valid	Other IRR onlyRADB, TC	211 31%	56
45.181.117.0/24	Valid	Other IRR onlyRADB, TC	211 31%	56
45.181.118.0/23	Valid	Other IRR onlyRADB, TC	211 31%	56
45.181.119.0/24	Valid	Other IRR onlyRADB, TC	211 31%	56
45.181.118.0/24	Valid	Other IRR onlyRADB, TC	210 31%	56

AS-SET

PeeringDB's irr_as_set for AS269221: TC::AS269221:AS-VIP-CONNECT. 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 (AS269221 isn't in the set, or no route object for AS269221 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	AS269221 in it	Not covered
TC::AS269221:AS-VIP-CONNECT	TC	2	3	526	Yes	0

Name

Database

ASNs

Sets

Route objects

AS269221 in it

Not covered

TC::AS269221:AS-VIP-CONNECT

526

Yes

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

Route object: RIR8
Route object: not announced510

Change	Prefix or set	Detail	Full-table peers
Route object: RIR	45.181.116.0/22	Route object only in RADB, TC. Add it in the RIR database for the space.	671 of 673
Route object: RIR	2804:6138::/32	Route object only in RADB, TC. Add it in the RIR database for the space.	636 of 636
Route object: RIR	45.181.116.0/23	Route object only in RADB, TC. Add it in the RIR database for the space.	211 of 673
Route object: RIR	45.181.116.0/24	Route object only in RADB, TC. Add it in the RIR database for the space.	211 of 673
Route object: RIR	45.181.117.0/24	Route object only in RADB, TC. Add it in the RIR database for the space.	211 of 673
Route object: RIR	45.181.118.0/23	Route object only in RADB, TC. Add it in the RIR database for the space.	211 of 673
Route object: RIR	45.181.119.0/24	Route object only in RADB, TC. Add it in the RIR database for the space.	211 of 673
Route object: RIR	45.181.118.0/24	Route object only in RADB, TC. Add it in the RIR database for the space.	210 of 673

Change

Prefix or set

Detail

Full-table peers

Route object: RIR

45.181.116.0/22