Routing security

AS33846 DATAPORT-AS

Unclassified RIPE

RPKI valid 11% 3 of 28 announcements

RPKI invalid 0 none

No ROA 25 not covered by any ROA

IRR registered 96% 1 missing · 0 other origin

ROAs 3 authorising this AS

Announcements

What this network originates

28 observed

Every prefix observed with AS33846 as its origin, checked against RPKI and the IRR. Problems sort first.

Prefix	RPKI	IRR	Vantage points
2a14:ae87:c000::/48	No ROA	No IRR	21
2a02:1002:d200::/40	No ROA	IRR covering	31
2a02:1002:da20::/48	No ROA	IRR covering	31
2a02:1002:da21::/48	No ROA	IRR covering	31
2a02:1002:da28::/48	No ROA	IRR covering	31
2a02:1002:da29::/48	No ROA	IRR covering	31
2a02:1002:da38::/48	No ROA	IRR covering	31
2a02:1002:da40::/48	No ROA	IRR covering	31
2a02:1002:da41::/48	No ROA	IRR covering	31
2a02:1002:da68::/48	No ROA	IRR covering	31
2a02:1002:da69::/48	No ROA	IRR covering	31
2a02:1002:da70::/48	No ROA	IRR covering	31
2a02:1002:da71::/48	No ROA	IRR covering	31
2a02:1002:da80::/48	No ROA	IRR covering	31
2a02:1002:da88::/48	No ROA	IRR covering	31
2a02:1002:da90::/48	No ROA	IRR covering	31
2a02:1002:daf0::/48	No ROA	IRR covering	31
2a02:1002:daf8::/48	No ROA	IRR covering	31
2a02:1002:daf9::/48	No ROA	IRR covering	31
2a02:1002:f0ff::/48	No ROA	IRR covering	31
2a02:1008:4::/48	No ROA	IRR covering	31
2a02:1008:4300::/48	No ROA	IRR covering	31
2a02:1008:4302::/48	No ROA	IRR covering	31
193.17.28.0/22	No ROA	IRR	53
193.168.236.0/22	No ROA	IRR	53
141.91.0.0/16	RPKI valid	IRR	53
164.133.230.0/24	RPKI valid	IRR	53
185.223.104.0/22	RPKI valid	IRR	53

RPKI · ROAs

Route origin authorisations

3 ROAs

Signed statements by address holders that AS33846 may originate these prefixes, up to the maximum length shown.

Prefix	Max length	Trust anchor
141.91.0.0/16	/24	RIPENCC
164.133.230.0/24	/24	RIPENCC
185.223.104.0/22	/22	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

10 objects · 5 not announced

Route objects naming AS33846 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
141.91.161.0/24	RIPE	—	`TNG-MNT`	2023-04-05	Not announced
141.91.175.0/24	RIPE	—	`TNG-MNT`	2023-04-05	Not announced
193.101.67.0/24	RIPE	DATAPORT	`TNG-MNT`	2004-09-13	Not announced
2a02:1002::/32	RIPE	—	`DE-GOV-HH-MNT`	2022-06-21	Not announced
2a02:1008::/32	RIPE	—	`DE-GOV-HH-MNT`	2022-06-21	Not announced
141.91.0.0/16	RIPE	DATAPORT	`TNG-MNT`	2026-09-25	Announced
164.133.230.0/24	RIPE	Ministerium fuer Infrastruktur und Digitales	`DE-GOV-ST-MNT`	2022-05-20	Announced
185.223.104.0/22	RIPE	DATAPORT	`TNG-MNT`	2017-12-06	Announced
193.17.28.0/22	RIPE	MELUNDSH	`DE-MINISTRY-1-MNT`	2018-09-14	Announced
193.168.236.0/22	RIPE	FHB-NET	`DE-BREMEN-1-MNT`	2020-11-04	Announced

IRR

AS-sets

The as-set is what upstreams expand to build this network's customer filter. Sets that list AS33846 directly show who expects to carry it.

AS-set	Where	Relationship
`AS-DATAPORT`	RIPE	Lists AS33846 as a direct member
`AS-VT-TRANSIT`	RIPE	Lists AS33846 as a direct member
`AS174:AS-COGC-036`	RADB	Lists AS33846 as a direct member
`AS198949:AS-SD`	RADB	Lists AS33846 as a direct member

RPKI from rpki-client, validated 2026-10-13 12:16 UTC. IRR from ARIN, RADB, RIPE, ALTDB, APNIC, LACNIC, NTTCOM, AFRINIC, collected 2026-10-13. Cross-check on bgp.he.net.