bgpreport

Network · data from 2026-11-12

AS263067 VNT FIBRAS

Registry name: AS263067 - VNT FIBRAS, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS263067, 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:5550:100::/40 No ROA Nonecovered by 2804:5550::/32 77 12% 29
2804:5550:7691::/48 No ROA Nonecovered by 2804:5550::/32 77 12% 29
45.165.176.0/22 No ROA Other IRR onlyRADB, TC 672 100% 67
2804:5550::/32 No ROA Other IRR onlyRADB, TC 636 100% 67
45.165.178.0/23 No ROA Other IRR onlyTC 91 14% 30
45.165.176.0/23 No ROA Other IRR onlyTC 90 13% 30
45.165.176.0/24 No ROA Other IRR onlyTC 90 13% 30
45.165.177.0/24 No ROA Other IRR onlyTC 90 13% 30
45.165.178.0/24 No ROA Other IRR onlyTC 90 13% 30
45.165.179.0/24 No ROA Other IRR onlyTC 90 13% 30
2804:5550:face::/48 No ROA Other IRR onlyTC 77 12% 29

AS-SET

PeeringDB's irr_as_set for AS263067: AS263067:AS-VNTFIBRAS. 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 (AS263067 isn't in the set, or no route object for AS263067 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 objectsAS263067 in itNot covered
AS263067:AS-VNTFIBRAS TC 4151 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 22 are in fix.csv.

  • ROA: none11
  • Route object: none2
  • Route object: RIR9
ChangePrefix or setDetailFull-table peers
ROA: none2804:5550:100::/40No ROA covers it. Add a ROA for AS263067, maxLength 40.77 of 636
Route object: none2804:5550:100::/40No route object for it. A route object for 2804:5550::/32 with origin AS263067 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263067 in the RIR database for the space.77 of 636
ROA: none2804:5550:7691::/48No ROA covers it. Add a ROA for AS263067, maxLength 48.77 of 636
Route object: none2804:5550:7691::/48No route object for it. A route object for 2804:5550::/32 with origin AS263067 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263067 in the RIR database for the space.77 of 636
ROA: none45.165.176.0/22No ROA covers it. Add a ROA for AS263067, maxLength 22.672 of 673
Route object: RIR45.165.176.0/22Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
ROA: none2804:5550::/32No ROA covers it. Add a ROA for AS263067, maxLength 32.636 of 636
Route object: RIR2804:5550::/32Route object only in RADB, TC. Add it in the RIR database for the space.636 of 636
ROA: none45.165.178.0/23No ROA covers it. Add a ROA for AS263067, maxLength 23.91 of 673
Route object: RIR45.165.178.0/23Route object only in TC. Add it in the RIR database for the space.91 of 673
ROA: none45.165.176.0/23No ROA covers it. Add a ROA for AS263067, maxLength 23.90 of 673
Route object: RIR45.165.176.0/23Route object only in TC. Add it in the RIR database for the space.90 of 673
ROA: none45.165.176.0/24No ROA covers it. Add a ROA for AS263067, maxLength 24.90 of 673
Route object: RIR45.165.176.0/24Route object only in TC. Add it in the RIR database for the space.90 of 673
ROA: none45.165.177.0/24No ROA covers it. Add a ROA for AS263067, maxLength 24.90 of 673
Route object: RIR45.165.177.0/24Route object only in TC. Add it in the RIR database for the space.90 of 673
ROA: none45.165.178.0/24No ROA covers it. Add a ROA for AS263067, maxLength 24.90 of 673
Route object: RIR45.165.178.0/24Route object only in TC. Add it in the RIR database for the space.90 of 673
ROA: none45.165.179.0/24No ROA covers it. Add a ROA for AS263067, maxLength 24.90 of 673
Route object: RIR45.165.179.0/24Route object only in TC. Add it in the RIR database for the space.90 of 673
ROA: none2804:5550:face::/48No ROA covers it. Add a ROA for AS263067, maxLength 48.77 of 636
Route object: RIR2804:5550:face::/48Route object only in TC. Add it in the RIR database for the space.77 of 636

Route objects not announced

Every route object with origin AS263067 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.