bgpreport

Network · data from 2026-11-12

AS268685 DCV SERVICOS DE LOCACAO DE MAQUINAS E EQUIPAMENTOS

Registry name: AS268685 - DCV SERVICOS DE LOCACAO DE MAQUINAS E EQUIPAMENTOS, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS268685, 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.164.92.0/22 No ROA Other IRR onlyRADB, TC 671 100% 66
45.164.92.0/24 No ROA Other IRR onlyTC 208 31% 56
45.164.93.0/24 No ROA Other IRR onlyTC 208 31% 56
45.164.94.0/24 No ROA Other IRR onlyRADB, TC 208 31% 56
45.164.95.0/24 No ROA Other IRR onlyRADB, TC 208 31% 56

AS-SET

PeeringDB's irr_as_set for AS268685: AS28216:AS-HOSTONE AS268685:RS-DCV. 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 (AS268685 isn't in the set, or no route object for AS268685 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 objectsAS268685 in itNot covered
AS28216:AS-HOSTONE TC 2124 Yes 0
AS268685:RS-DCV A route-set, not an AS-SET; route-sets aren't expanded.

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

  • ROA: none5
  • Route object: RIR5
  • Route object: not announced8
ChangePrefix or setDetailFull-table peers
ROA: none45.164.92.0/22No ROA covers it. Add a ROA for AS268685, maxLength 22.671 of 673
Route object: RIR45.164.92.0/22Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
ROA: none45.164.92.0/24No ROA covers it. Add a ROA for AS268685, maxLength 24.208 of 673
Route object: RIR45.164.92.0/24Route object only in TC. Add it in the RIR database for the space.208 of 673
ROA: none45.164.93.0/24No ROA covers it. Add a ROA for AS268685, maxLength 24.208 of 673
Route object: RIR45.164.93.0/24Route object only in TC. Add it in the RIR database for the space.208 of 673
ROA: none45.164.94.0/24No ROA covers it. Add a ROA for AS268685, maxLength 24.208 of 673
Route object: RIR45.164.94.0/24Route object only in RADB, TC. Add it in the RIR database for the space.208 of 673
ROA: none45.164.95.0/24No ROA covers it. Add a ROA for AS268685, maxLength 24.208 of 673
Route object: RIR45.164.95.0/24Route object only in RADB, TC. Add it in the RIR database for the space.208 of 673

Route objects not announced

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

45.164.92.0/23RADB, TCNo ROA
45.164.94.0/23RADB, TCNo ROA
2804:5508::/32TCNo ROA
2804:5508:4::/46TCNo ROA
2804:5508:4::/48TCNo ROA
2804:5508:5::/48TCNo ROA
2804:5508:6::/48TCNo ROA
2804:5508:7::/48TCNo 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.