bgpreport

Network · data from 2026-11-12

AS14886 AS14886 - Atos Origin Brasil Ltda

Registry name: AS14886 - Atos Origin Brasil Ltda, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS14886, 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.237.96.0/20 No ROA None 668 99% 67
200.192.80.0/20 No ROA Other IRR onlyRADB 669 99% 67

AS-SET

AS14886 isn't in PeeringDB, where networks name their 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 6 are in fix.csv.

  • ROA: none2
  • Route object: none1
  • Route object: RIR1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none200.237.96.0/20No ROA covers it. Add a ROA for AS14886, maxLength 20.668 of 673
Route object: none200.237.96.0/20No route object for it. Add a route object with origin AS14886 in the RIR database for the space.668 of 673
ROA: none200.192.80.0/20No ROA covers it. Add a ROA for AS14886, maxLength 20.669 of 673
Route object: RIR200.192.80.0/20Route object only in RADB. Add it in the RIR database for the space.669 of 673

Route objects not announced

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

129.214.1.0/24RIPENo ROA
185.75.230.0/24RADBNo 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.