Routing security
AS198944 TN-TELE-DATA-AS *** IPv4 Peering ***
Unclassified RIPE
Announcements
What this network originates
Every prefix observed with AS198944 as its origin, checked against RPKI and the IRR. Problems sort first.
| Prefix | RPKI | IRR | Vantage points |
|---|---|---|---|
| 2a03:6960::/32 | RPKI valid | IRR | 30 |
| 81.161.96.0/23 | RPKI valid | IRR | 52 |
| 185.82.228.0/22 | RPKI valid | IRR | 52 |
| 185.137.112.0/23 | RPKI valid | IRR | 52 |
| 185.137.114.0/23 | RPKI valid | IRR | 52 |
| 185.247.100.0/22 | RPKI valid | IRR | 52 |
| 2001:67c:2a68::/48 | RPKI valid | IRR | 30 |
RPKI · ROAs
Route origin authorisations
Signed statements by address holders that AS198944 may originate these prefixes, up to the maximum length shown.
| Prefix | Max length | Trust anchor |
|---|---|---|
| 81.161.96.0/23 | /23 | RIPENCC |
| 185.82.228.0/22 | /22 | RIPENCC |
| 185.137.112.0/23 | /23 | RIPENCC |
| 185.137.114.0/23 | /23 | RIPENCC |
| 185.247.100.0/22 | /22 | RIPENCC |
| 2001:67c:2a68::/48 | /48 | RIPENCC |
| 2a03:6960::/32 | /32 | 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 |
|---|---|---|---|
| AS3292 | TDC Holding A/S | Declared | Observed |
| AS31027 | GlobalConnect A/S | 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 AS198944 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 |
|---|---|---|---|---|---|
| 2a03:a560::/32 | RIPE | TN-Tele-IPv6-Route-Obj. | MNT-THOMASKRUSE | 2017-04-07 | Not announced |
| 81.161.96.0/23 | RIPE | TN-Tele-IPv4-Route-Obj. | MNT-THOMASKRUSE | 2020-09-21 | Announced |
| 185.82.228.0/22 | RIPE | TN-Tele-IPv4-Route-Obj. | MNT-THOMASKRUSE | 2017-09-16 | Announced |
| 185.137.112.0/23 | RIPE | TN-Tele-IPv4-Route-Obj. | MNT-THOMASKRUSE | 2016-02-27 | Announced |
| 185.137.114.0/23 | RIPE | TN-Hosting-IPv4-Route-Obj. | MNT-THOMASKRUSE | 2021-05-28 | Announced |
| 185.247.100.0/22 | RIPE | TN-Tele-IPv4-Route-Obj. | MNT-THOMASKRUSE | 2021-02-11 | Announced |
| 2001:67c:2a68::/48 | RIPE | TN-Tele-IPv6-Route-Obj. | MNT-BODATA | 2013-12-05 | Announced |
| 2a03:6960::/32 | RIPE | TN-Tele-IPv6-Route-Obj. | MNT-THOMASKRUSE | 2015-01-02 | Announced |
IRR
AS-sets
The as-set is what upstreams expand to build this network's customer filter. Sets that list AS198944 directly show who expects to carry it.
| AS-set | Where | Relationship |
|---|---|---|
AS-TDCNETDK | RIPE | Lists AS198944 as a direct member |
AS31027:AS-GCNET-LEGACY | RIPE | Lists AS198944 as a direct member |
AS31027:AS-NIANET | RIPE | Lists AS198944 as a direct member |
RPKI from rpki-client, validated 2026-10-19 12:02 UTC. IRR from ARIN, RADB, RIPE, ALTDB, APNIC, LACNIC, NTTCOM, AFRINIC, collected 2026-10-19. Cross-check on bgp.he.net.