bgpreport

Network · data from 2026-11-12

AS270561 net rapida telecomunicações do brasil

Registry name: AS270561 - R O R COMERCIO E SERVICOS LTDA, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS270561, 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:6de0::/34 Invalid: maxLength Nonecovered by 2804:6de0::/32 5 1%low visibility 5
189.85.116.0/24 Valid Other IRR onlyRADB, TC 672 100% 67
189.85.117.0/24 Valid Other IRR onlyRADB, TC 672 100% 67
189.85.118.0/23 Valid Other IRR onlyRADB, TC 670 100% 67
2804:6de0::/32 Valid Other IRR onlyALTDB, RADB, TC 635 100% 67
2804:6de0:4000::/34 Valid Other IRR onlyTC 635 100% 67
2804:6de0:c000::/34 Valid Other IRR onlyTC 635 100% 67
2804:6de0:8000::/34 Valid Other IRR onlyTC 634 100% 67

AS-SET

PeeringDB's irr_as_set for AS270561: TC::AS270561:RS-ROUTES. 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 (AS270561 isn't in the set, or no route object for AS270561 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 objectsAS270561 in itNot covered
TC::AS270561:RS-ROUTES 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 15 are in fix.csv.

  • ROA: maxLength1
  • Route object: none1
  • Route object: RIR7
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
ROA: maxLength2804:6de0::/34ROA 2804:6de0::/32 AS270561 has maxLength 32; the route is a /34. Raise the maxLength, or add a ROA for 2804:6de0::/34.5 of 636
Route object: none2804:6de0::/34No route object for it. A route object for 2804:6de0::/32 with origin AS270561 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270561 in the RIR database for the space.5 of 636
Route object: RIR189.85.116.0/24Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR189.85.117.0/24Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR189.85.118.0/23Route object only in RADB, TC. Add it in the RIR database for the space.670 of 673
Route object: RIR2804:6de0::/32Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:6de0:4000::/34Route object only in TC. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:6de0:c000::/34Route object only in TC. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:6de0:8000::/34Route object only in TC. Add it in the RIR database for the space.634 of 636

Route objects not announced

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

189.85.116.0/22ALTDB, RADB, TCValid
189.85.116.0/23TCValid
189.85.118.0/24RADB, TCValid
189.85.119.0/24RADB, TCValid
2804:63a8::/32ALTDBInvalid: origin
2804:63a8:f000::/40ALTDBInvalid: origin

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.