bgpreport

Network · data from 2026-11-12

AS8055 Tavola 8055

Registry name: AS8055 - TAVOLA CONECTIVIDADE LTDA., BR · PeeringDB

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

Announced routes

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

200.160.56.0/22 Valid Nonecovered by 200.160.48.0/20 220 33% 57
187.84.96.0/22 Valid Nonecovered by 187.84.96.0/20 219 33% 57
187.84.96.0/20 Valid Other IRR onlyRADB 671 100% 66
200.160.48.0/20 Valid Other IRR onlyRADB 670 100% 66
2804:4c::/32 Valid Other IRR onlyRADB 635 100% 67

AS-SET

AS8055's PeeringDB record names no AS-SET.

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

  • Route object: none2
  • Route object: RIR3
  • Route object: not announced32
ChangePrefix or setDetailFull-table peers
Route object: none200.160.56.0/22No route object for it. A route object for 200.160.48.0/20 with origin AS8055 covers it (filters allowing more-specifics accept it). Add a route object with origin AS8055 in the RIR database for the space.220 of 673
Route object: none187.84.96.0/22No route object for it. A route object for 187.84.96.0/20 with origin AS8055 covers it (filters allowing more-specifics accept it). Add a route object with origin AS8055 in the RIR database for the space.219 of 673
Route object: RIR187.84.96.0/20Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR200.160.48.0/20Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR2804:4c::/32Route object only in RADB. Add it in the RIR database for the space.635 of 636

Route objects not announced

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

187.84.96.0/24RADBValid
187.84.97.0/24RADBValid
187.84.98.0/24RADBValid
187.84.99.0/24RADBValid
187.84.100.0/24RADBValid
187.84.101.0/24RADBValid
187.84.102.0/24RADBValid
187.84.103.0/24RADBValid
187.84.104.0/24RADBValid
187.84.105.0/24RADBValid
187.84.106.0/24RADBValid
187.84.107.0/24RADBValid
187.84.108.0/24RADBValid
187.84.109.0/24RADBValid
187.84.110.0/24RADBValid
187.84.111.0/24RADBValid
200.160.48.0/24RADBValid
200.160.49.0/24RADBValid
200.160.50.0/24RADBValid
200.160.51.0/24RADBValid
200.160.52.0/24RADBValid
200.160.53.0/24RADBValid
200.160.54.0/24RADBValid
200.160.55.0/24RADBValid
200.160.56.0/24RADBValid
200.160.57.0/24RADBValid
200.160.58.0/24RADBValid
200.160.59.0/24RADBValid
200.160.60.0/24RADBValid
200.160.61.0/24RADBValid
200.160.62.0/24RADBValid
200.160.63.0/24RADBValid

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.