Routing security
AS57544 ZFORT-AS
Unclassified RIPE
Announcements
What this network originates
Every prefix observed with AS57544 as its origin, checked against RPKI and the IRR. Problems sort first.
| Prefix | RPKI | IRR | Vantage points |
|---|---|---|---|
| 91.232.178.0/23 | RPKI valid | IRR | 54 |
RPKI · ROAs
Route origin authorisations
Signed statements by address holders that AS57544 may originate these prefixes, up to the maximum length shown.
| Prefix | Max length | Trust anchor |
|---|---|---|
| 91.232.178.0/23 | /24 | 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 |
|---|---|---|---|
| AS1820 | WNET TELECOM USA Corp. | 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 AS57544 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.232.178.0/23 | RIPE | — | RIPE-DB-MNT | 2026-01-23 | Announced |
IRR
AS-sets
The as-set is what upstreams expand to build this network's customer filter. Sets that list AS57544 directly show who expects to carry it.
| AS-set | Where | Relationship |
|---|---|---|
AS-BANKINFORM | RIPE | Lists AS57544 as a direct member |
AS-NEWLINE | RIPE | Lists AS57544 as a direct member |
AS-WTUC | ARIN | Lists AS57544 as a direct member |
AS21011:AS-CLIENTS | RIPE | Lists AS57544 as a direct member |
AS3326:AS-CLIENTS | RIPE | Lists AS57544 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.