bgpreport

Network · data from 2026-11-12

AS266220 RFS Tecnologia

Registry name: AS266220 - RFS Tecnologia LTDA, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS266220, 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:3c90:b8::/48 No ROA Nonecovered by 2804:3c90::/32 636 100% 69
2804:3c90:800::/38 No ROA Nonecovered by 2804:3c90::/32 636 100% 69
2804:3c90:3b80::/42 No ROA Nonecovered by 2804:3c90::/32 636 100% 69
2804:3c90:c40::/42 No ROA Nonecovered by 2804:3c90::/32 635 100% 69
2804:3c90:3800::/48 No ROA Nonecovered by 2804:3c90::/32 635 100% 69
192.145.216.0/22 No ROA Other IRR onlyRADB 671 100% 67
192.145.216.0/24 No ROA Other IRR onlyRADB 671 100% 67
192.145.217.0/24 No ROA Other IRR onlyRADB 671 100% 67
192.145.218.0/24 No ROA Other IRR onlyRADB 671 100% 67
192.145.219.0/24 No ROA Other IRR onlyRADB 671 100% 67
2804:3c90::/32 No ROA Other IRR onlyRADB 636 100% 69

AS-SET

PeeringDB's irr_as_set for AS266220: AS266220:AS-RFS. 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 (AS266220 isn't in the set, or no route object for AS266220 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 objectsAS266220 in itNot covered
AS266220:AS-RFS RADBlists itself further down2 member sets in no database: AS-RMS, AS-SNT-28604 4724538 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 26 are in fix.csv.

  • ROA: none11
  • Route object: none5
  • Route object: RIR6
  • AS-SET: missing member2
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none2804:3c90:b8::/48No ROA covers it. Add a ROA for AS266220, maxLength 48.636 of 636
Route object: none2804:3c90:b8::/48No route object for it. A route object for 2804:3c90::/32 with origin AS266220 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266220 in the RIR database for the space.636 of 636
ROA: none2804:3c90:800::/38No ROA covers it. Add a ROA for AS266220, maxLength 38.636 of 636
Route object: none2804:3c90:800::/38No route object for it. A route object for 2804:3c90::/32 with origin AS266220 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266220 in the RIR database for the space.636 of 636
ROA: none2804:3c90:3b80::/42No ROA covers it. Add a ROA for AS266220, maxLength 42.636 of 636
Route object: none2804:3c90:3b80::/42No route object for it. A route object for 2804:3c90::/32 with origin AS266220 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266220 in the RIR database for the space.636 of 636
ROA: none2804:3c90:c40::/42No ROA covers it. Add a ROA for AS266220, maxLength 42.635 of 636
Route object: none2804:3c90:c40::/42No route object for it. A route object for 2804:3c90::/32 with origin AS266220 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266220 in the RIR database for the space.635 of 636
ROA: none2804:3c90:3800::/48No ROA covers it. Add a ROA for AS266220, maxLength 48.635 of 636
Route object: none2804:3c90:3800::/48No route object for it. A route object for 2804:3c90::/32 with origin AS266220 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266220 in the RIR database for the space.635 of 636
ROA: none192.145.216.0/22No ROA covers it. Add a ROA for AS266220, maxLength 22.671 of 673
Route object: RIR192.145.216.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none192.145.216.0/24No ROA covers it. Add a ROA for AS266220, maxLength 24.671 of 673
Route object: RIR192.145.216.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none192.145.217.0/24No ROA covers it. Add a ROA for AS266220, maxLength 24.671 of 673
Route object: RIR192.145.217.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none192.145.218.0/24No ROA covers it. Add a ROA for AS266220, maxLength 24.671 of 673
Route object: RIR192.145.218.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none192.145.219.0/24No ROA covers it. Add a ROA for AS266220, maxLength 24.671 of 673
Route object: RIR192.145.219.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none2804:3c90::/32No ROA covers it. Add a ROA for AS266220, maxLength 32.636 of 636
Route object: RIR2804:3c90::/32Route object only in RADB. Add it in the RIR database for the space.636 of 636
AS-SET: missing memberAS266220:AS-RFSAS266220:AS-RFS (RADB) lists AS-RMS; no IRR database read has it.
AS-SET: missing memberAS266220:AS-RFSAS266220:AS-RFS (RADB) lists AS-SNT-28604; no IRR database read has it.

Route objects not announced

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

192.145.216.0/23RADBNo ROA
192.145.218.0/23RADBNo 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.