bgpreport

Network · data from 2026-11-12

AS268207 RVT SERVICOS DE TELECOMUNICAÇÕES

Registry name: AS268207 - RVT SERVICOS DE TELECOMUNICACOES LTDA, BR · PeeringDB

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

Announced routes

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

38.224.144.0/23 No ROA Nonecovered by 38.224.144.0/22 10 1%low visibility 6
206.0.92.0/23 No ROA Nonecovered by 206.0.92.0/22 10 1%low visibility 6
206.0.94.0/23 No ROA Nonecovered by 206.0.92.0/22 10 1%low visibility 6
38.224.144.0/22 No ROA Other IRR onlyRADB 672 100% 66
206.0.92.0/22 No ROA Other IRR onlyRADB 671 100% 66
45.235.52.0/22 Valid Other IRR onlyNTTCOM, RADB, TC 672 100% 66
200.225.112.0/22 Valid Other IRR onlyTC 670 100% 66
2804:4d98::/32 Valid Other IRR onlyNTTCOM, RADB, TC 632 99% 67
45.235.52.0/23 Valid Other IRR onlyTC 10 1%low visibility 6
45.235.54.0/23 Valid Other IRR onlyTC 10 1%low visibility 6
200.225.112.0/23 Valid Other IRR onlyTC 10 1%low visibility 6
200.225.114.0/23 Valid Other IRR onlyTC 10 1%low visibility 6
2804:4d98::/33 Valid Other IRR onlyTC 10 2%low visibility 6
2804:4d98:8000::/33 Valid Other IRR onlyTC 10 2%low visibility 6

AS-SET

PeeringDB's irr_as_set for AS268207: AS268207: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 (AS268207 isn't in the set, or no route object for AS268207 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 objectsAS268207 in itNot covered
AS268207:AS-CUSTOMERS TC 2145 No 14

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

  • ROA: none5
  • Route object: none3
  • Route object: RIR11
  • AS-SET: own ASN1
  • Route object: not announced16
ChangePrefix or setDetailFull-table peers
ROA: none38.224.144.0/23No ROA covers it. Add a ROA for AS268207, maxLength 23.10 of 673
Route object: none38.224.144.0/23No route object for it. A route object for 38.224.144.0/22 with origin AS268207 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268207 in the RIR database for the space.10 of 673
ROA: none206.0.92.0/23No ROA covers it. Add a ROA for AS268207, maxLength 23.10 of 673
Route object: none206.0.92.0/23No route object for it. A route object for 206.0.92.0/22 with origin AS268207 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268207 in the RIR database for the space.10 of 673
ROA: none206.0.94.0/23No ROA covers it. Add a ROA for AS268207, maxLength 23.10 of 673
Route object: none206.0.94.0/23No route object for it. A route object for 206.0.92.0/22 with origin AS268207 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268207 in the RIR database for the space.10 of 673
ROA: none38.224.144.0/22No ROA covers it. Add a ROA for AS268207, maxLength 22.672 of 673
Route object: RIR38.224.144.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none206.0.92.0/22No ROA covers it. Add a ROA for AS268207, maxLength 22.671 of 673
Route object: RIR206.0.92.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR45.235.52.0/22Route object only in NTTCOM, RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR200.225.112.0/22Route object only in TC. Add it in the RIR database for the space.670 of 673
Route object: RIR2804:4d98::/32Route object only in NTTCOM, RADB, TC. Add it in the RIR database for the space.632 of 636
Route object: RIR45.235.52.0/23Route object only in TC. Add it in the RIR database for the space.10 of 673
Route object: RIR45.235.54.0/23Route object only in TC. Add it in the RIR database for the space.10 of 673
Route object: RIR200.225.112.0/23Route object only in TC. Add it in the RIR database for the space.10 of 673
Route object: RIR200.225.114.0/23Route object only in TC. Add it in the RIR database for the space.10 of 673
Route object: RIR2804:4d98::/33Route object only in TC. Add it in the RIR database for the space.10 of 636
Route object: RIR2804:4d98:8000::/33Route object only in TC. Add it in the RIR database for the space.10 of 636
AS-SET: own ASNAS268207:AS-CUSTOMERSAS268207 isn't in AS268207:AS-CUSTOMERS (TC) once expanded. Add AS268207 to it.

Route objects not announced

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

45.235.52.0/24TCValid
45.235.53.0/24TCValid
45.235.54.0/24TCValid
45.235.55.0/24TCValid
200.225.112.0/24TCValid
200.225.113.0/24TCValid
200.225.114.0/24TCValid
200.225.115.0/24TCValid
2804:4d98::/34TCValid
2804:4d98:3::/48TCValid
2804:4d98:10::/48TCValid
2804:4d98:4000::/34TCValid
2804:4d98:8000::/34TCValid
2804:4d98:8000::/48TCValid
2804:4d98:c000::/34TCValid
2804:4d98:c000::/38RADBValid

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.