Network · data from 2026-11-12

AS219359 Edge Core FZE

Registry name: EDGE-AS Edge Core FZE, AE · PeeringDB

16IPv4 routes 93.8% RPKI valid · 93.8% with a route object

1IPv6 routes 100.0% RPKI valid · 100.0% with a route object

1RPKI invalid 1 origin · 0 maxLength

0No ROA 1 with no route object for this origin

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

2Route objects not announced registered with origin AS219359, seen from no peer

Announced routes

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


77.110.107.0/24	Invalid: origin	None	40 6%low visibility	26
132.243.160.0/24	Valid	RIR databaseRIPE	673 100%	66
132.243.167.0/24	Valid	RIR databaseRIPE	673 100%	67
132.243.186.0/24	Valid	RIR databaseRIPE	673 100%	67
157.228.64.0/24	Valid	RIR databaseRIPE	673 100%	67
157.228.69.0/24	Valid	RIR databaseRIPE	673 100%	67
185.113.8.0/24	Valid	RIR databaseRIPE	673 100%	67
132.243.187.0/24	Valid	RIR databaseRIPE	672 100%	67
157.228.65.0/24	Valid	RIR databaseRIPE	672 100%	67
157.228.68.0/24	Valid	RIR databaseRIPE	672 100%	67
45.86.60.0/24	Valid	RIR databaseRIPE	671 100%	67
132.243.173.0/24	Valid	RIR databaseRIPE	671 100%	67
157.228.67.0/24	Valid	RIR databaseRIPE	671 100%	68
132.243.163.0/24	Valid	RIR databaseRIPE	670 100%	68
157.228.71.0/24	Valid	RIR databaseRIPE	669 99%	67
157.228.66.0/24	Valid	RIR databaseRIPE	667 99%	67
2a05:1640:1::/48	Valid	RIR databaseRIPE	635 100%	69

77.110.107.0/24

Invalid: origin

None

40 6%low visibility

132.243.160.0/24

Valid

RIR databaseRIPE

673 100%

132.243.167.0/24

Valid

RIR databaseRIPE

673 100%

132.243.186.0/24

Valid

RIR databaseRIPE

673 100%

157.228.64.0/24

Valid

RIR databaseRIPE

673 100%

157.228.69.0/24

Valid

RIR databaseRIPE

673 100%

185.113.8.0/24

Valid

RIR databaseRIPE

673 100%

132.243.187.0/24

Valid

RIR databaseRIPE

672 100%

157.228.65.0/24

Valid

RIR databaseRIPE

672 100%

157.228.68.0/24

Valid

RIR databaseRIPE

672 100%

45.86.60.0/24

Valid

RIR databaseRIPE

671 100%

132.243.173.0/24

Valid

RIR databaseRIPE

671 100%

157.228.67.0/24

Valid

RIR databaseRIPE

671 100%

132.243.163.0/24

Valid

RIR databaseRIPE

670 100%

157.228.71.0/24

Valid

RIR databaseRIPE

669 99%

157.228.66.0/24

Valid

RIR databaseRIPE

667 99%

2a05:1640:1::/48

Valid

RIR databaseRIPE

635 100%

AS-SET

AS219359'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 4 are in fix.csv.

ROA: origin1
Route object: none1
Route object: not announced2

Change	Prefix or set	Detail	Full-table peers
ROA: origin	77.110.107.0/24	ROAs covering it name AS35629, not AS219359. If AS219359 should announce it, add a ROA for AS219359.	40 of 673
Route object: none	77.110.107.0/24	No route object for it. Add a route object with origin AS219359 in the RIR database for the space.	40 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: origin

77.110.107.0/24

ROAs covering it name AS35629, not AS219359. If AS219359 should announce it, add a ROA for AS219359.

40 of 673

Route object: none

77.110.107.0/24

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

40 of 673

Route objects not announced

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


157.228.70.0/24	RIPE	Valid
2a05:541:129::/48	RIPE	Valid

157.228.70.0/24

RIPE

Valid

2a05:541:129::/48

RIPE

Valid

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.