bgpreport

Network · data from 2026-11-12

AS53139 RDF Telecom

Registry name: AS53139 - RDF Informatica Ltda, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS53139, 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:31d4::/33 Valid Nonecovered by 2804:31d4::/32 114 18% 41
2804:31d4:8000::/33 Valid Nonecovered by 2804:31d4::/32 114 18% 41
2804:31d4::/34 Valid Nonecovered by 2804:31d4::/32 70 11% 33
2804:31d4:4000::/34 Valid Nonecovered by 2804:31d4::/32 70 11% 33
2804:31d4:8000::/34 Valid Nonecovered by 2804:31d4::/32 70 11% 33
2804:31d4:c000::/34 Valid Nonecovered by 2804:31d4::/32 70 11% 33
168.197.204.0/22 Valid Other IRR onlyALTDB, RADB 672 100% 66
168.197.204.0/23 Valid Other IRR onlyRADB 672 100% 66
168.197.206.0/23 Valid Other IRR onlyRADB 672 100% 66
187.109.80.0/20 Valid Other IRR onlyALTDB, RADB, TC 672 100% 66
187.109.80.0/23 Valid Other IRR onlyRADB 672 100% 66
187.109.82.0/23 Valid Other IRR onlyRADB 672 100% 66
187.109.84.0/23 Valid Other IRR onlyRADB 672 100% 66
187.109.86.0/23 Valid Other IRR onlyRADB 672 100% 66
187.109.88.0/23 Valid Other IRR onlyRADB 672 100% 66
187.109.90.0/23 Valid Other IRR onlyRADB 672 100% 66
187.109.92.0/23 Valid Other IRR onlyRADB 672 100% 66
187.109.94.0/23 Valid Other IRR onlyRADB 672 100% 66
2804:31d4::/32 Valid Other IRR onlyALTDB, RADB 630 99% 69
168.197.204.0/24 Valid Other IRR onlyRADB 336 50% 61
187.109.80.0/24 Valid Other IRR onlyRADB 336 50% 61
187.109.81.0/24 Valid Other IRR onlyRADB 336 50% 61
187.109.83.0/24 Valid Other IRR onlyRADB 336 50% 61
187.109.84.0/24 Valid Other IRR onlyRADB 336 50% 61
187.109.85.0/24 Valid Other IRR onlyRADB 336 50% 61
187.109.86.0/24 Valid Other IRR onlyRADB 336 50% 61
187.109.87.0/24 Valid Other IRR onlyRADB 336 50% 61
187.109.94.0/24 Valid Other IRR onlyRADB 336 50% 61
168.197.205.0/24 Valid Other IRR onlyRADB 335 50% 61
168.197.206.0/24 Valid Other IRR onlyRADB 335 50% 61
168.197.207.0/24 Valid Other IRR onlyRADB 335 50% 61
187.109.82.0/24 Valid Other IRR onlyRADB 335 50% 61
187.109.88.0/24 Valid Other IRR onlyRADB 335 50% 61
187.109.89.0/24 Valid Other IRR onlyRADB 335 50% 61
187.109.90.0/24 Valid Other IRR onlyRADB 335 50% 61
187.109.91.0/24 Valid Other IRR onlyRADB 335 50% 61
187.109.92.0/24 Valid Other IRR onlyRADB 335 50% 61
187.109.93.0/24 Valid Other IRR onlyRADB 335 50% 61
187.109.95.0/24 Valid Other IRR onlyRADB 335 50% 61

AS-SET

PeeringDB's irr_as_set for AS53139: AS53139:AS-ALL. 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 (AS53139 isn't in the set, or no route object for AS53139 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 objectsAS53139 in itNot covered
AS53139:AS-ALL ALTDB 2146 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 39 are in fix.csv.

  • Route object: none6
  • Route object: RIR33
ChangePrefix or setDetailFull-table peers
Route object: none2804:31d4::/33No route object for it. A route object for 2804:31d4::/32 with origin AS53139 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53139 in the RIR database for the space.114 of 636
Route object: none2804:31d4:8000::/33No route object for it. A route object for 2804:31d4::/32 with origin AS53139 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53139 in the RIR database for the space.114 of 636
Route object: none2804:31d4::/34No route object for it. A route object for 2804:31d4::/32 with origin AS53139 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53139 in the RIR database for the space.70 of 636
Route object: none2804:31d4:4000::/34No route object for it. A route object for 2804:31d4::/32 with origin AS53139 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53139 in the RIR database for the space.70 of 636
Route object: none2804:31d4:8000::/34No route object for it. A route object for 2804:31d4::/32 with origin AS53139 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53139 in the RIR database for the space.70 of 636
Route object: none2804:31d4:c000::/34No route object for it. A route object for 2804:31d4::/32 with origin AS53139 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53139 in the RIR database for the space.70 of 636
Route object: RIR168.197.204.0/22Route object only in ALTDB, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR168.197.204.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR168.197.206.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR187.109.80.0/20Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR187.109.80.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR187.109.82.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR187.109.84.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR187.109.86.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR187.109.88.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR187.109.90.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR187.109.92.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR187.109.94.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR2804:31d4::/32Route object only in ALTDB, RADB. Add it in the RIR database for the space.630 of 636
Route object: RIR168.197.204.0/24Route object only in RADB. Add it in the RIR database for the space.336 of 673
Route object: RIR187.109.80.0/24Route object only in RADB. Add it in the RIR database for the space.336 of 673
Route object: RIR187.109.81.0/24Route object only in RADB. Add it in the RIR database for the space.336 of 673
Route object: RIR187.109.83.0/24Route object only in RADB. Add it in the RIR database for the space.336 of 673
Route object: RIR187.109.84.0/24Route object only in RADB. Add it in the RIR database for the space.336 of 673
Route object: RIR187.109.85.0/24Route object only in RADB. Add it in the RIR database for the space.336 of 673
Route object: RIR187.109.86.0/24Route object only in RADB. Add it in the RIR database for the space.336 of 673
Route object: RIR187.109.87.0/24Route object only in RADB. Add it in the RIR database for the space.336 of 673
Route object: RIR187.109.94.0/24Route object only in RADB. Add it in the RIR database for the space.336 of 673
Route object: RIR168.197.205.0/24Route object only in RADB. Add it in the RIR database for the space.335 of 673
Route object: RIR168.197.206.0/24Route object only in RADB. Add it in the RIR database for the space.335 of 673
Route object: RIR168.197.207.0/24Route object only in RADB. Add it in the RIR database for the space.335 of 673
Route object: RIR187.109.82.0/24Route object only in RADB. Add it in the RIR database for the space.335 of 673
Route object: RIR187.109.88.0/24Route object only in RADB. Add it in the RIR database for the space.335 of 673
Route object: RIR187.109.89.0/24Route object only in RADB. Add it in the RIR database for the space.335 of 673
Route object: RIR187.109.90.0/24Route object only in RADB. Add it in the RIR database for the space.335 of 673
Route object: RIR187.109.91.0/24Route object only in RADB. Add it in the RIR database for the space.335 of 673
Route object: RIR187.109.92.0/24Route object only in RADB. Add it in the RIR database for the space.335 of 673
Route object: RIR187.109.93.0/24Route object only in RADB. Add it in the RIR database for the space.335 of 673
Route object: RIR187.109.95.0/24Route object only in RADB. Add it in the RIR database for the space.335 of 673

Route objects not announced

Every route object with origin AS53139 is announced.

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.