bgpreport

Network · data from 2026-11-12

AS269180 VIPNET Conexão

Registry name: AS269180 - VIPNET Conexao, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS269180, 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.104.0/22 No ROA Other IRR onlyALTDB, RADB, TC 672 100% 66
2804:609c::/32 No ROA Other IRR onlyALTDB, RADB, TC 635 100% 67
45.181.104.0/23 No ROA Other IRR onlyALTDB, RADB, TC 127 19% 44
45.181.106.0/23 No ROA Other IRR onlyALTDB, RADB, TC 127 19% 44
2804:609c::/33 No ROA Other IRR onlyALTDB, RADB, TC 115 18% 43
2804:609c:8000::/33 No ROA Other IRR onlyALTDB, RADB, TC 115 18% 43
45.181.104.0/24 No ROA Other IRR onlyALTDB, RADB, TC 4 1%low visibility 4
45.181.105.0/24 No ROA Other IRR onlyALTDB, RADB, TC 4 1%low visibility 4
45.181.106.0/24 No ROA Other IRR onlyALTDB, RADB, TC 4 1%low visibility 4
45.181.107.0/24 No ROA Other IRR onlyALTDB, RADB, TC 4 1%low visibility 4
144.225.121.0/24 Valid RIR databaseARIN, RADB 672 100% 66

AS-SET

PeeringDB's irr_as_set for AS269180: ALTDB::AS269180:AS-CUSTOMERS. 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 (AS269180 isn't in the set, or no route object for AS269180 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.

NameDatabaseASNsSets Route objectsAS269180 in itNot covered
ALTDB::AS269180:AS-CUSTOMERS ALTDB 7179 Yes 0

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

  • ROA: none10
  • Route object: RIR10
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none45.181.104.0/22No ROA covers it. Add a ROA for AS269180, maxLength 22.672 of 673
Route object: RIR45.181.104.0/22Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.672 of 673
ROA: none2804:609c::/32No ROA covers it. Add a ROA for AS269180, maxLength 32.635 of 636
Route object: RIR2804:609c::/32Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.635 of 636
ROA: none45.181.104.0/23No ROA covers it. Add a ROA for AS269180, maxLength 23.127 of 673
Route object: RIR45.181.104.0/23Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.127 of 673
ROA: none45.181.106.0/23No ROA covers it. Add a ROA for AS269180, maxLength 23.127 of 673
Route object: RIR45.181.106.0/23Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.127 of 673
ROA: none2804:609c::/33No ROA covers it. Add a ROA for AS269180, maxLength 33.115 of 636
Route object: RIR2804:609c::/33Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.115 of 636
ROA: none2804:609c:8000::/33No ROA covers it. Add a ROA for AS269180, maxLength 33.115 of 636
Route object: RIR2804:609c:8000::/33Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.115 of 636
ROA: none45.181.104.0/24No ROA covers it. Add a ROA for AS269180, maxLength 24.4 of 673
Route object: RIR45.181.104.0/24Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.4 of 673
ROA: none45.181.105.0/24No ROA covers it. Add a ROA for AS269180, maxLength 24.4 of 673
Route object: RIR45.181.105.0/24Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.4 of 673
ROA: none45.181.106.0/24No ROA covers it. Add a ROA for AS269180, maxLength 24.4 of 673
Route object: RIR45.181.106.0/24Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.4 of 673
ROA: none45.181.107.0/24No ROA covers it. Add a ROA for AS269180, maxLength 24.4 of 673
Route object: RIR45.181.107.0/24Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.4 of 673

Route objects not announced

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

2804:609c::/34ALTDB, TCNo ROA
2804:609c:4000::/34ALTDB, TCNo ROA
2804:609c:8000::/34ALTDB, TCNo ROA
2804:609c:c000::/34ALTDB, TCNo ROA

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.