bgpreport

Network · data from 2026-11-12

AS264880 RF Connect

Registry name: AS264880 - RF Connect Provedor de Acesso LTDA, BR · PeeringDB

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

Announced routes

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

177.72.50.0/24 No ROA Other origin only 0 0%low visibility 1
2804:2f40:fec0::/42 Valid Nonecovered by 2804:2f40:f000::/36 636 100% 67
2804:2f40:ff00::/42 Valid Nonecovered by 2804:2f40:f000::/36 636 100% 67
168.227.56.0/22 Valid Other IRR onlyRADB, TC 672 100% 67
168.227.56.0/24 Valid Other IRR onlyRADB 672 100% 67
168.227.59.0/24 Valid Other IRR onlyRADB 672 100% 67
170.246.185.0/24 Valid Other IRR onlyRADB 671 100% 67
170.246.187.0/24 Valid Other IRR onlyRADB 671 100% 67
170.246.186.0/23 Valid Other IRR onlyRADB 670 100% 67
170.246.186.0/24 Valid Other IRR onlyRADB 670 100% 67
170.246.184.0/24 Valid Other IRR onlyRADB 669 99% 67
2804:2f40::/32 Valid Other IRR onlyRADB, TC 636 100% 67

AS-SET

PeeringDB's irr_as_set for AS264880: AS264880:AS-GLOBAL. 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 (AS264880 isn't in the set, or no route object for AS264880 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 objectsAS264880 in itNot covered
AS264880:AS-GLOBAL TC 52205 Yes 1

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

  • ROA: none1
  • Route object: none3
  • Route object: RIR9
  • Route object: not announced36
ChangePrefix or setDetailFull-table peers
ROA: none177.72.50.0/24No ROA covers it. Add a ROA for AS264880, maxLength 24.0 of 673
Route object: none177.72.50.0/24Route objects for it name AS262541. Add a route object with origin AS264880 in the RIR database for the space.0 of 673
Route object: none2804:2f40:fec0::/42No route object for it. A route object for 2804:2f40:f000::/36 with origin AS264880 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264880 in the RIR database for the space.636 of 636
Route object: none2804:2f40:ff00::/42No route object for it. A route object for 2804:2f40:f000::/36 with origin AS264880 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264880 in the RIR database for the space.636 of 636
Route object: RIR168.227.56.0/22Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR168.227.56.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR168.227.59.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR170.246.185.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR170.246.187.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR170.246.186.0/23Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR170.246.186.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR170.246.184.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR2804:2f40::/32Route object only in RADB, TC. Add it in the RIR database for the space.636 of 636

Route objects not announced

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

168.227.56.0/23RADBValid
168.227.57.0/24RADBValid
168.227.58.0/23RADBValid
168.227.58.0/24RADBValid
170.246.184.0/22RADB, TCValid
170.246.184.0/23RADBValid
2804:2f40::/33RADBValid
2804:2f40::/34RADBValid
2804:2f40::/35RADBValid
2804:2f40::/36RADBValid
2804:2f40:1000::/36RADBValid
2804:2f40:2000::/35RADBValid
2804:2f40:2000::/36RADBValid
2804:2f40:3000::/36RADBValid
2804:2f40:4000::/34RADBValid
2804:2f40:4000::/35RADBValid
2804:2f40:4000::/36RADBValid
2804:2f40:5000::/36RADBValid
2804:2f40:6000::/35RADBValid
2804:2f40:6000::/36RADBValid
2804:2f40:7000::/36RADBValid
2804:2f40:8000::/33RADBValid
2804:2f40:8000::/34RADBValid
2804:2f40:8000::/35RADBValid
2804:2f40:8000::/36RADBValid
2804:2f40:9000::/36RADBValid
2804:2f40:a000::/35RADBValid
2804:2f40:a000::/36RADBValid
2804:2f40:b000::/36RADBValid
2804:2f40:c000::/34RADBValid
2804:2f40:c000::/35RADBValid
2804:2f40:c000::/36RADBValid
2804:2f40:d000::/36RADBValid
2804:2f40:e000::/35RADBValid
2804:2f40:e000::/36RADBValid
2804:2f40:f000::/36RADBValid

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.