bgpreport

Network · data from 2026-11-12

AS265495 rr serviços

Registry name: AS265495 - RR SERVICOS LTDA, BR · PeeringDB

4IPv4 routes 0.0% 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
7No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
6Route objects not announced registered with origin AS265495, seen from no peer

Announced routes

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

170.78.53.0/24 No ROA Other IRR onlyNTTCOM, RADB, TC 671 100% 67
170.78.52.0/24 No ROA Other IRR onlyRADB, TC 669 99% 67
170.78.54.0/24 No ROA Other IRR onlyRADB, TC 669 99% 67
170.78.55.0/24 No ROA Other IRR onlyRADB, TC 669 99% 67
2804:3504::/40 No ROA Other IRR onlyTC 635 100% 69
2804:3504:200::/40 No ROA Other IRR onlyTC 635 100% 67
2804:3504:ff00::/40 No ROA Other IRR onlyRADB, TC 635 100% 69

AS-SET

PeeringDB's irr_as_set for AS265495: AS265495:AS-CONE. 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 (AS265495 isn't in the set, or no route object for AS265495 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 objectsAS265495 in itNot covered
AS265495:AS-CONE TC2 member sets in no database: AS265463:AS-GLOBAL, AS267420:AS-NORTENET 377208,848 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: none7
  • Route object: RIR7
  • AS-SET: missing member2
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
ROA: none170.78.53.0/24No ROA covers it. Add a ROA for AS265495, maxLength 24.671 of 673
Route object: RIR170.78.53.0/24Route object only in NTTCOM, RADB, TC. Add it in the RIR database for the space.671 of 673
ROA: none170.78.52.0/24No ROA covers it. Add a ROA for AS265495, maxLength 24.669 of 673
Route object: RIR170.78.52.0/24Route object only in RADB, TC. Add it in the RIR database for the space.669 of 673
ROA: none170.78.54.0/24No ROA covers it. Add a ROA for AS265495, maxLength 24.669 of 673
Route object: RIR170.78.54.0/24Route object only in RADB, TC. Add it in the RIR database for the space.669 of 673
ROA: none170.78.55.0/24No ROA covers it. Add a ROA for AS265495, maxLength 24.669 of 673
Route object: RIR170.78.55.0/24Route object only in RADB, TC. Add it in the RIR database for the space.669 of 673
ROA: none2804:3504::/40No ROA covers it. Add a ROA for AS265495, maxLength 40.635 of 636
Route object: RIR2804:3504::/40Route object only in TC. Add it in the RIR database for the space.635 of 636
ROA: none2804:3504:200::/40No ROA covers it. Add a ROA for AS265495, maxLength 40.635 of 636
Route object: RIR2804:3504:200::/40Route object only in TC. Add it in the RIR database for the space.635 of 636
ROA: none2804:3504:ff00::/40No ROA covers it. Add a ROA for AS265495, maxLength 40.635 of 636
Route object: RIR2804:3504:ff00::/40Route object only in RADB, TC. Add it in the RIR database for the space.635 of 636
AS-SET: missing memberAS265495:AS-CONEAS265495:AS-CONE (TC) lists AS265463:AS-GLOBAL; no IRR database read has it.
AS-SET: missing memberAS265495:AS-CONEAS265495:AS-CONE (TC) lists AS267420:AS-NORTENET; no IRR database read has it.

Route objects not announced

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

170.78.52.0/22NTTCOM, RADB, TCNo ROA
170.78.52.0/23RADB, TCNo ROA
170.78.54.0/23RADB, TCNo ROA
2804:3504::/32NTTCOM, RADB, TCNo ROA
2804:3504::/42TCNo ROA
2804:3504:ffff::/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.