Network · data from 2026-11-12

AS27784 AS27784 - Bco. Pichincha Matriz

Registry name: AS27784 - Bco. Pichincha Matriz, EC · not in PeeringDB

5IPv4 routes 40.0% RPKI valid · 40.0% with a route object

0IPv6 routes

0RPKI invalid 0 origin · 0 maxLength

3No ROA 3 with no route object for this origin

3Low visibility seen by under 10% of full-table peers

4Route objects not announced registered with origin AS27784, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS27784, 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.31.27.32/27	No ROA	None	2 0%low visibility	2
200.32.71.64/27	No ROA	None	2 0%low visibility	2
200.41.114.96/27	No ROA	None	2 0%low visibility	2
200.115.43.0/24	Valid	Other IRR onlyRADB	671 100%	67
200.115.42.0/24	Valid	Other IRR onlyRADB	670 100%	67

200.31.27.32/27

No ROA

None

2 0%low visibility

200.32.71.64/27

No ROA

None

2 0%low visibility

200.41.114.96/27

No ROA

None

2 0%low visibility

200.115.43.0/24

Valid

Other IRR onlyRADB

671 100%

200.115.42.0/24

Valid

Other IRR onlyRADB

670 100%

AS-SET

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

ROA: none3
Route object: none3
Route object: RIR2
Route object: not announced4

Change	Prefix or set	Detail	Full-table peers
ROA: none	200.31.27.32/27	No ROA covers it. Add a ROA for AS27784, maxLength 27.	2 of 673
Route object: none	200.31.27.32/27	No route object for it. Add a route object with origin AS27784 in the RIR database for the space.	2 of 673
ROA: none	200.32.71.64/27	No ROA covers it. Add a ROA for AS27784, maxLength 27.	2 of 673
Route object: none	200.32.71.64/27	No route object for it. Add a route object with origin AS27784 in the RIR database for the space.	2 of 673
ROA: none	200.41.114.96/27	No ROA covers it. Add a ROA for AS27784, maxLength 27.	2 of 673
Route object: none	200.41.114.96/27	No route object for it. Add a route object with origin AS27784 in the RIR database for the space.	2 of 673
Route object: RIR	200.115.43.0/24	Route object only in RADB. Add it in the RIR database for the space.	671 of 673
Route object: RIR	200.115.42.0/24	Route object only in RADB. Add it in the RIR database for the space.	670 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: none

200.31.27.32/27

No ROA covers it. Add a ROA for AS27784, maxLength 27.

2 of 673

Route object: none

200.31.27.32/27

No route object for it. Add a route object with origin AS27784 in the RIR database for the space.

2 of 673

ROA: none

200.32.71.64/27

No ROA covers it. Add a ROA for AS27784, maxLength 27.

2 of 673

Route object: none

200.32.71.64/27

No route object for it. Add a route object with origin AS27784 in the RIR database for the space.

2 of 673

ROA: none

200.41.114.96/27

No ROA covers it. Add a ROA for AS27784, maxLength 27.

2 of 673

Route object: none

200.41.114.96/27

No route object for it. Add a route object with origin AS27784 in the RIR database for the space.

2 of 673

Route object: RIR

200.115.43.0/24

Route object only in RADB. Add it in the RIR database for the space.

671 of 673

Route object: RIR

200.115.42.0/24

Route object only in RADB. Add it in the RIR database for the space.

670 of 673

Route objects not announced

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


179.0.204.0/24	RADB	Valid
200.0.63.0/24	RADB	Valid
200.10.209.0/24	RADB	Valid
207.179.29.0/24	RADB, RIPE-NONAUTH	No ROA

179.0.204.0/24

RADB

Valid

200.0.63.0/24

RADB

Valid

200.10.209.0/24

RADB

Valid

207.179.29.0/24

RADB, RIPE-NONAUTH

No 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.