Routing security
AS43545 TELEDATA
Unclassified APNIC
Announcements
What this network originates
Every prefix observed with AS43545 as its origin, checked against RPKI and the IRR. Problems sort first.
| Prefix | RPKI | IRR | Vantage points |
|---|---|---|---|
| 80.84.64.0/21 | No ROA | IRR | 52 |
| 2a02:24d0::/32 | RPKI valid | IRR | 31 |
| 2a02:24d0::/48 | RPKI valid | IRR | 31 |
| 77.74.104.0/21 | RPKI valid | IRR | 52 |
| 77.74.110.0/24 | RPKI valid | IRR covering | 51 |
| 78.40.144.0/21 | RPKI valid | IRR | 52 |
| 78.40.144.0/24 | RPKI valid | IRR | 51 |
| 78.40.146.0/24 | RPKI valid | IRR | 51 |
| 78.40.150.0/24 | RPKI valid | IRR | 51 |
| 78.40.151.0/24 | RPKI valid | IRR | 51 |
| 80.84.80.0/21 | RPKI valid | IRR | 52 |
| 80.84.88.0/21 | RPKI valid | IRR | 52 |
| 80.84.90.0/24 | RPKI valid | IRR covering | 51 |
| 185.113.216.0/24 | RPKI valid | IRR | 52 |
| 185.113.219.0/24 | RPKI valid | IRR | 52 |
| 212.84.65.0/24 | RPKI valid | IRR | 51 |
| 212.84.67.0/24 | RPKI valid | IRR | 51 |
| 212.84.69.0/24 | RPKI valid | IRR | 51 |
| 212.84.73.0/24 | RPKI valid | IRR | 51 |
RPKI · ROAs
Route origin authorisations
Signed statements by address holders that AS43545 may originate these prefixes, up to the maximum length shown.
| Prefix | Max length | Trust anchor |
|---|---|---|
| 77.74.104.0/21 | /21 | RIPENCC |
| 77.74.110.0/24 | /24 | RIPENCC |
| 78.40.144.0/21 | /21 | RIPENCC |
| 78.40.144.0/24 | /24 | RIPENCC |
| 78.40.146.0/24 | /24 | RIPENCC |
| 78.40.150.0/24 | /24 | RIPENCC |
| 78.40.151.0/24 | /24 | RIPENCC |
| 80.84.80.0/21 | /21 | RIPENCC |
| 80.84.86.0/24 | /24 | RIPENCC |
| 80.84.87.0/24 | /24 | RIPENCC |
| 80.84.88.0/21 | /21 | RIPENCC |
| 80.84.89.0/24 | /24 | RIPENCC |
| 80.84.90.0/24 | /24 | RIPENCC |
| 80.84.91.0/24 | /24 | RIPENCC |
| 85.202.196.0/22 | /22 | RIPENCC |
| 185.113.216.0/22 | /24 | RIPENCC |
| 185.113.216.0/24 | /24 | RIPENCC |
| 185.113.217.0/24 | /24 | RIPENCC |
| 185.113.218.0/24 | /24 | RIPENCC |
| 185.113.219.0/24 | /24 | RIPENCC |
| 212.84.64.0/21 | /24 | RIPENCC |
| 212.84.68.0/24 | /24 | RIPENCC |
| 212.84.72.0/21 | /24 | RIPENCC |
| 212.84.80.0/21 | /24 | RIPENCC |
| 212.84.88.0/21 | /24 | RIPENCC |
| 212.84.95.0/24 | /24 | RIPENCC |
| 2a02:24d0::/32 | /32 | RIPENCC |
| 2a02:24d0::/48 | /48 | RIPENCC |
ROA-based and RPKI-valid-only prefix lists for routers are on asn.ipinfo.app.
RPKI · ASPA
Declared transit providers
No ASPA record This network has not published an ASPA object. ASPA lets a network sign the list of its transit providers, so routers can reject paths that route through anyone else (route leaks). Only a few thousand networks publish one so far, so its absence is normal.
IRR
Registered route objects
Route objects naming AS43545 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 |
|---|---|---|---|---|---|
| 77.74.109.0/25 | RIPE | NCO Europe Ltd | MNT-TELE | 2022-06-28 | Not announced |
| 80.84.80.0/20 | RIPE | Network Teledata | MNT-TELE | 2017-02-10 | Not announced |
| 80.84.86.0/24 | RIPE | Teledata Trial Network | MNT-TELE | 2013-07-11 | Not announced |
| 80.84.87.0/24 | RIPE | Teledata Network | MNT-TELE | 2023-03-08 | Not announced |
| 85.202.196.0/22 | RIPE | — | MNT-TELE | 2019-10-28 | Not announced |
| 185.35.56.0/22 | RIPE | Route for AS43545 | MNT-VENOM | 2018-10-03 | Not announced |
| 185.35.56.0/23 | RIPE | Route for AS43545 | MNT-VENOM | 2018-10-14 | Not announced |
| 185.35.58.0/23 | RIPE | Route for AS43545 | MNT-VENOM | 2018-10-14 | Not announced |
| 185.113.216.0/22 | RIPE | TeleData UK Ltd - Transit Network 2 | MNT-TELE | 2021-09-16 | Not announced |
| 185.113.217.0/24 | RIPE | TeleData UK Ltd - Transit Network 2 | MNT-TELE | 2021-09-28 | Not announced |
| 185.113.218.0/24 | RIPE | TeleData UK Ltd - Transit Network 2 | MNT-TELE | 2021-09-28 | Not announced |
| 185.182.68.0/22 | RIPE | — | UK-TECHLOQ-1-MNT | 2018-03-16 | Not announced |
| 185.182.68.0/23 | RIPE | — | UK-TECHLOQ-1-MNT | 2023-02-02 | Not announced |
| 185.182.68.0/24 | RIPE | — | UK-TECHLOQ-1-MNT | 2023-02-02 | Not announced |
| 185.182.69.0/24 | RIPE | — | UK-TECHLOQ-1-MNT | 2023-02-02 | Not announced |
| 185.182.70.0/24 | RIPE | — | UK-TECHLOQ-1-MNT | 2023-02-02 | Not announced |
| 212.84.64.0/24 | RIPE | Teledata 1e | MNT-TELE | 2023-02-01 | Not announced |
| 212.84.66.0/24 | RIPE | Teledata 1e | MNT-TELE | 2023-02-01 | Not announced |
| 212.84.68.0/24 | RIPE | Teledata 1e | MNT-TELE | 2023-02-01 | Not announced |
| 212.84.70.0/24 | RIPE | Teledata 1e | MNT-TELE | 2023-02-01 | Not announced |
| 212.84.71.0/24 | RIPE | Teledata 1e | MNT-TELE | 2023-02-01 | Not announced |
| 212.84.72.0/24 | RIPE | Teledata 1e | MNT-TELE | 2023-02-01 | Not announced |
| 212.84.74.0/24 | RIPE | Teledata 1e | MNT-TELE | 2023-02-01 | Not announced |
| 212.84.75.0/24 | RIPE | Teledata 1e | MNT-TELE | 2023-02-01 | Not announced |
| 212.84.76.0/24 | RIPE | Teledata 1e | MNT-TELE | 2023-02-01 | Not announced |
| 2a0f:3680::/29 | RIPE | — | UK-TECHLOQ-1-MNT | 2019-09-25 | Not announced |
| 77.74.104.0/21 | RIPE | Teledata Manchester Block 2 | MNT-TELE | 2009-01-07 | Announced |
| 78.40.144.0/21 | RIPE | Teledata Manchester Block 1 | MNT-TELE | 2008-08-29 | Announced |
| 78.40.144.0/24 | RIPE | Teledata Network 78.40.144.0 | MNT-TELE | 2013-07-16 | Announced |
| 78.40.146.0/24 | RIPE | Teledata Network 78.40.146.0 | MNT-TELE | 2016-03-14 | Announced |
| 78.40.150.0/24 | RIPE | Teledata Network 78.40.150.0 | MNT-TELE | 2016-03-14 | Announced |
| 78.40.151.0/24 | RIPE | — | MNT-TELE | 2026-02-02 | Announced |
| 80.84.64.0/21 | RIPE | Teledata Network Stockport | MNT-TELE | 2017-02-10 | Announced |
| 80.84.80.0/21 | RIPE | Network Stockport | MNT-TELE | 2017-02-10 | Announced |
| 80.84.88.0/21 | RIPE | Network Teledata | MNT-TELE | 2017-02-10 | Announced |
| 185.113.216.0/24 | RIPE | TeleData UK Ltd - Transit Network 2 | MNT-TELE | 2021-09-28 | Announced |
| 185.113.219.0/24 | RIPE | TeleData UK Ltd - Transit Network 2 | MNT-TELE | 2021-09-28 | Announced |
| 212.84.65.0/24 | RIPE | Teledata 1e | MNT-TELE | 2023-02-01 | Announced |
| 212.84.67.0/24 | RIPE | Teledata 1e | MNT-TELE | 2023-02-01 | Announced |
| 212.84.69.0/24 | RIPE | Teledata 1e | MNT-TELE | 2023-02-01 | Announced |
| 212.84.73.0/24 | RIPE | Teledata 1e | MNT-TELE | 2023-02-01 | Announced |
| 2a02:24d0::/32 | RIPE | Teledata IPV6 route M22 Block | MNT-TELE | 2014-04-12 | Announced |
| 2a02:24d0::/48 | RIPE | Teledata IPV6 route M22 | MNT-TELE | 2013-06-26 | Announced |
IRR
AS-sets
The as-set is what upstreams expand to build this network's customer filter. Sets that list AS43545 directly show who expects to carry it.
| AS-set | Where | Relationship |
|---|---|---|
AS-IOMART | RIPE | Lists AS43545 as a direct member |
AS-NEXTCONNEX | RIPE | Lists AS43545 as a direct member |
AS-RETN-ACTUAL-V4 | RIPE | Lists AS43545 as a direct member |
AS-TELEDATAUK | RIPE | Lists AS43545 as a direct member |
RPKI from rpki-client, validated 2026-10-14 18:17 UTC. IRR from ARIN, RADB, RIPE, ALTDB, APNIC, LACNIC, NTTCOM, AFRINIC, collected 2026-10-14. Cross-check on bgp.he.net.