bgpreport

Network · data from 2026-11-12

AS267396 Rv Connect telecomunicações

Registry name: AS267396 - Rv Connect telecomunicacoes Ltda - Me., BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS267396, 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.233.202.0/23 No ROA Other IRR onlyRADB 671 100% 66
45.233.202.0/24 Valid Other IRR onlyRADB, TC 671 100% 66
45.233.200.0/24 Valid Other IRR onlyRADB, TC 668 99% 66
45.233.201.0/24 Valid Other IRR onlyRADB, TC 668 99% 66
45.233.203.0/24 Valid Other IRR onlyRADB, TC 667 99% 66
2804:4cd8::/35 Valid Other IRR onlyRADB 636 100% 67
2804:4cd8:4000::/35 Valid Other IRR onlyRADB 636 100% 67
2804:4cd8:4000::/37 Valid Other IRR onlyRADB 636 100% 67
2804:4cd8:4800::/37 Valid Other IRR onlyRADB 636 100% 67
2804:4cd8:5000::/37 Valid Other IRR onlyRADB 636 100% 67
2804:4cd8:5800::/37 Valid Other IRR onlyRADB 636 100% 67
2804:4cd8:8000::/35 Valid Other IRR onlyRADB 636 100% 67
2804:4cd8:8000::/37 Valid Other IRR onlyRADB, TC 636 100% 67
2804:4cd8:8800::/37 Valid Other IRR onlyRADB 636 100% 67
2804:4cd8:9000::/37 Valid Other IRR onlyRADB, TC 636 100% 67
2804:4cd8:a000::/35 Valid Other IRR onlyRADB 636 100% 67
2804:4cd8:a000::/37 Valid Other IRR onlyRADB 636 100% 67
2804:4cd8:a800::/37 Valid Other IRR onlyRADB 636 100% 67
2804:4cd8:b000::/37 Valid Other IRR onlyRADB 636 100% 67
2804:4cd8:b800::/37 Valid Other IRR onlyRADB 636 100% 67
2804:4cd8:c000::/35 Valid Other IRR onlyRADB 636 100% 67
2804:4cd8:2000::/35 Valid Other IRR onlyRADB 635 100% 67
2804:4cd8:9800::/37 Valid Other IRR onlyRADB 1 0%low visibility 1

AS-SET

PeeringDB's irr_as_set for AS267396: AS-RVCONNECT. 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 (AS267396 isn't in the set, or no route object for AS267396 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 objectsAS267396 in itNot covered
AS-RVCONNECT In no IRR database read today.

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

  • ROA: none1
  • Route object: RIR23
  • AS-SET: not found1
  • Route object: not announced19
ChangePrefix or setDetailFull-table peers
ROA: none45.233.202.0/23No ROA covers it. Add a ROA for AS267396, maxLength 23.671 of 673
Route object: RIR45.233.202.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR45.233.202.0/24Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR45.233.200.0/24Route object only in RADB, TC. Add it in the RIR database for the space.668 of 673
Route object: RIR45.233.201.0/24Route object only in RADB, TC. Add it in the RIR database for the space.668 of 673
Route object: RIR45.233.203.0/24Route object only in RADB, TC. Add it in the RIR database for the space.667 of 673
Route object: RIR2804:4cd8::/35Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR2804:4cd8:4000::/35Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR2804:4cd8:4000::/37Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR2804:4cd8:4800::/37Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR2804:4cd8:5000::/37Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR2804:4cd8:5800::/37Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR2804:4cd8:8000::/35Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR2804:4cd8:8000::/37Route object only in RADB, TC. Add it in the RIR database for the space.636 of 636
Route object: RIR2804:4cd8:8800::/37Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR2804:4cd8:9000::/37Route object only in RADB, TC. Add it in the RIR database for the space.636 of 636
Route object: RIR2804:4cd8:a000::/35Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR2804:4cd8:a000::/37Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR2804:4cd8:a800::/37Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR2804:4cd8:b000::/37Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR2804:4cd8:b800::/37Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR2804:4cd8:c000::/35Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR2804:4cd8:2000::/35Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:4cd8:9800::/37Route object only in RADB. Add it in the RIR database for the space.1 of 636
AS-SET: not foundAS-RVCONNECTPeeringDB names AS-RVCONNECT; no IRR database read has it.

Route objects not announced

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

45.233.200.0/22RADB, TCNo ROA
45.233.200.0/23RADB, TCNo ROA
2804:4cd8::/32RADB, TCNo ROA
2804:4cd8::/37RADBValid
2804:4cd8::/40RADBValid
2804:4cd8::/48RADBValid
2804:4cd8:4::/48RADBValid
2804:4cd8:8::/48RADBValid
2804:4cd8:c::/48RADBValid
2804:4cd8:800::/37RADBValid
2804:4cd8:800::/40RADBValid
2804:4cd8:1000::/37RADBValid
2804:4cd8:1800::/37RADBValid
2804:4cd8:4104::/46RADBValid
2804:4cd8:8000::/33RADBNo ROA
2804:4cd8:8000::/40RADBValid
2804:4cd8:8100::/45RADBValid
2804:4cd8:8400::/45RADBValid
2804:4cd8:8800::/40RADBValid

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.