Routing security
AS50419 EXASTACK
Unclassified RIPE Cable/DSL/ISP
Announcements
What this network originates
Every prefix observed with AS50419 as its origin, checked against RPKI and the IRR. Problems sort first.
| Prefix | RPKI | IRR | Vantage points |
|---|---|---|---|
| 109.95.184.0/24 | RPKI valid | IRR | 52 |
| 109.95.185.0/24 | RPKI valid | IRR | 52 |
| 2001:67c:118::/48 | RPKI valid | IRR | 30 |
RPKI · ROAs
Route origin authorisations
Signed statements by address holders that AS50419 may originate these prefixes, up to the maximum length shown.
| Prefix | Max length | Trust anchor |
|---|---|---|
| 109.95.184.0/24 | /24 | RIPENCC |
| 109.95.185.0/24 | /24 | RIPENCC |
| 109.95.190.0/24 | /24 | RIPENCC |
| 2001:67c:118::/48 | /48 | RIPENCC |
ROA-based and RPKI-valid-only prefix lists for routers are on asn.ipinfo.app.
RPKI · ASPA
Declared transit providers
This network has signed an ASPA record naming its transit providers. Each is compared against the upstreams observed in routing paths.
| AS | Network | ASPA | Routing paths |
|---|---|---|---|
| AS47227 | Charles Briscoe-Smith trading as Servology | Declared | Observed |
An observed upstream that is not declared is not necessarily a leak: our upstream inference cannot tell a transit provider from a peer seen in the same position. A declared provider that is never observed is usually a backup path.
IRR
Registered route objects
Route objects naming AS50419 as origin, across RADb, the RIR registries, ALTDB and NTTCOM. Objects that are registered but not announced come first: a stale object lets anyone who can spoof this origin through an IRR-built filter.
| Prefix | Source | Description | Maintainer | Changed | Routing |
|---|---|---|---|---|---|
| 91.244.239.0/24 | RIPE | Eye Pea v4 Network | EXST-MNT | 2012-08-24 | Not announced |
| 109.95.184.0/21 | RIPE | exaStack IPv4 | EXST-MNT | 2012-08-06 | Not announced |
| 109.95.188.0/24 | RIPE | exaStack IPv4 | EXST-MNT | 2017-08-19 | Not announced |
| 109.95.189.0/24 | RIPE | exaStack IPv4 | EXST-MNT | 2017-08-19 | Not announced |
| 109.95.190.0/24 | RIPE | exaStack IPv4 | EXST-MNT | 2017-08-19 | Not announced |
| 109.95.184.0/24 | RIPE | exaStack IPv4 | EXST-MNT | 2017-08-19 | Announced |
| 109.95.185.0/24 | RIPE | exaStack IPv4 | EXST-MNT | 2017-08-19 | Announced |
| 2001:67c:118::/48 | RIPE | exaStack IPv6 | EXST-MNT | 2012-07-11 | Announced |
IRR
AS-sets
The as-set is what upstreams expand to build this network's customer filter. Sets that list AS50419 directly show who expects to carry it.
| AS-set | Where | Relationship |
|---|---|---|
AS-EXASTACK | PeeringDB | Declared by the operator as its own set |
AS-AA | RIPE | Lists AS50419 as a direct member |
AS-C4L | RIPE | Lists AS50419 as a direct member |
AS-EXASTACK | RIPE | Lists AS50419 as a direct member |
AS-SERVOLOGY | RIPE | Lists AS50419 as a direct member |
AS-TSONE | RIPE | Lists AS50419 as a direct member |
RPKI from rpki-client, validated 2026-10-21 12:00 UTC. IRR from ARIN, RADB, RIPE, ALTDB, APNIC, LACNIC, NTTCOM, AFRINIC, collected 2026-10-21. Cross-check on bgp.he.net.