bgpreport

Network · data from 2026-11-12

AS52762 TRIADE FIBRA

Registry name: AS52762 - TRIADE FIBRA, BR · PeeringDB

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

Announced routes

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

216.28.208.0/23 No ROA Other IRR onlyRADB 668 99% 67
2804:b7c::/34 Valid Nonecovered by 2804:b7c::/33 345 54% 64
216.28.198.0/24 Valid Nonecovered by 216.28.196.0/22 332 49% 61
216.28.196.0/24 Valid Nonecovered by 216.28.196.0/22 330 49% 61
216.28.197.0/24 Valid Nonecovered by 216.28.196.0/22 330 49% 61
216.28.196.0/23 Valid Nonecovered by 216.28.196.0/22 2 0%low visibility 2
177.23.28.0/23 Valid Other IRR onlyTC 671 100% 66
177.23.28.0/24 Valid Other IRR onlyTC 671 100% 67
177.23.29.0/24 Valid Other IRR onlyTC 671 100% 67
177.23.30.0/23 Valid Other IRR onlyTC 671 100% 66
177.23.30.0/24 Valid Other IRR onlyTC 671 100% 67
177.23.31.0/24 Valid Other IRR onlyTC 671 100% 67
38.156.0.0/23 Valid Other IRR onlyRADB 670 100% 67
38.156.0.0/24 Valid Other IRR onlyRADB 670 100% 67
38.156.1.0/24 Valid Other IRR onlyRADB 670 100% 67
38.156.2.0/23 Valid Other IRR onlyRADB 670 100% 67
38.156.2.0/24 Valid Other IRR onlyRADB 670 100% 67
38.156.3.0/24 Valid Other IRR onlyRADB 670 100% 67
216.28.200.0/24 Valid Other IRR onlyRADB 670 100% 66
216.28.201.0/24 Valid Other IRR onlyRADB 670 100% 66
216.28.202.0/24 Valid Other IRR onlyRADB 670 100% 66
216.28.203.0/24 Valid Other IRR onlyRADB 670 100% 66
216.28.204.0/24 Valid Other IRR onlyRADB 670 100% 66
216.28.205.0/24 Valid Other IRR onlyRADB 670 100% 66
216.28.206.0/24 Valid Other IRR onlyRADB 670 100% 66
216.28.207.0/24 Valid Other IRR onlyRADB 670 100% 66
177.23.28.0/22 Valid Other IRR onlyTC 668 99% 67
2804:b7c::/32 Valid Other IRR onlyRADB, TC 632 99% 67
2804:b7c:4000::/34 Valid Other IRR onlyTC 345 54% 64
2804:b7c:8000::/34 Valid Other IRR onlyTC 345 54% 64
2804:b7c:c000::/34 Valid Other IRR onlyTC 345 54% 64
2804:b7c::/33 Valid Other IRR onlyTC 110 17% 42
2804:b7c:8000::/33 Valid Other IRR onlyTC 110 17% 42
38.156.0.0/22 Valid RIR databaseARIN, RADB 668 99% 67
206.0.140.0/24 Valid RIR databaseARIN, RADB 668 99% 67
206.0.141.0/24 Valid RIR databaseARIN, RADB 668 99% 66
206.0.142.0/24 Valid RIR databaseARIN, RADB 668 99% 66
216.28.196.0/22 Valid RIR databaseARIN 668 99% 67
216.28.200.0/21 Valid RIR databaseARIN, RADB 668 99% 67

AS-SET

PeeringDB's irr_as_set for AS52762: AS52762. 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 (AS52762 isn't in the set, or no route object for AS52762 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 objectsAS52762 in itNot covered
AS52762 A single AS number, not a set: AS52762 (this network), 43 route objects.

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

  • ROA: none1
  • Route object: none5
  • Route object: RIR28
  • Route object: not announced9
ChangePrefix or setDetailFull-table peers
ROA: none216.28.208.0/23No ROA covers it. Add a ROA for AS52762, maxLength 23.668 of 673
Route object: RIR216.28.208.0/23Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: none2804:b7c::/34No route object for it. A route object for 2804:b7c::/33 with origin AS52762 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52762 in the RIR database for the space.345 of 636
Route object: none216.28.198.0/24No route object for it. A route object for 216.28.196.0/22 with origin AS52762 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52762 in the RIR database for the space.332 of 673
Route object: none216.28.196.0/24No route object for it. A route object for 216.28.196.0/22 with origin AS52762 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52762 in the RIR database for the space.330 of 673
Route object: none216.28.197.0/24No route object for it. A route object for 216.28.196.0/22 with origin AS52762 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52762 in the RIR database for the space.330 of 673
Route object: none216.28.196.0/23No route object for it. A route object for 216.28.196.0/22 with origin AS52762 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52762 in the RIR database for the space.2 of 673
Route object: RIR177.23.28.0/23Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR177.23.28.0/24Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR177.23.29.0/24Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR177.23.30.0/23Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR177.23.30.0/24Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR177.23.31.0/24Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR38.156.0.0/23Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR38.156.0.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR38.156.1.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR38.156.2.0/23Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR38.156.2.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR38.156.3.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR216.28.200.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR216.28.201.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR216.28.202.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR216.28.203.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR216.28.204.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR216.28.205.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR216.28.206.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR216.28.207.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR177.23.28.0/22Route object only in TC. Add it in the RIR database for the space.668 of 673
Route object: RIR2804:b7c::/32Route object only in RADB, TC. Add it in the RIR database for the space.632 of 636
Route object: RIR2804:b7c:4000::/34Route object only in TC. Add it in the RIR database for the space.345 of 636
Route object: RIR2804:b7c:8000::/34Route object only in TC. Add it in the RIR database for the space.345 of 636
Route object: RIR2804:b7c:c000::/34Route object only in TC. Add it in the RIR database for the space.345 of 636
Route object: RIR2804:b7c::/33Route object only in TC. Add it in the RIR database for the space.110 of 636
Route object: RIR2804:b7c:8000::/33Route object only in TC. Add it in the RIR database for the space.110 of 636

Route objects not announced

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

206.0.140.0/22RADBNo ROA
206.0.140.0/23RADBNo ROA
206.0.142.0/23RADBNo ROA
216.28.200.0/22RADBValid
216.28.200.0/23RADBValid
216.28.202.0/23RADBValid
216.28.204.0/22RADBValid
216.28.204.0/23RADBValid
216.28.206.0/23RADBValid

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.