subnet.im

141.90.14.0/24

AS20546 is not currently observed originating this prefix. The origins we do see are listed above.

At a glance

Addresses

256

/24 block

Visibility

100%

78 of 78 vantage points

RPKI

No ROA

Registry

RIPE NCCDE

Allocated 8th April 1994

AS paths to this prefix

One real path per vantage point, fanning out from the origin. Where two reach the prefix the same way, those hops are drawn once. Open a path to follow it hop by hop.

OriginVantage points
AS path graph: 5 observed paths to 141.90.14.0/24, fanning out from AS29515 toward the vantage points that see it. Each path is written out in full beneath the graph.AS29515Hessische Zentral…OriginAS28676WiTCOM Wiesbadene…AS8298IPng Networks GmbHAS8529Zain Omantel Inte…AS4230Claro (Embratel)AS35280F5 Networks SARLAS33891Core-Backbone GmbHAS23673Cogetel Online, C…AS8551Bezeq Internation…AS42013Together Communic…
  1. Amsterdam29515286768298This path
  2. London, UK29515286768529This path
  3. Sao Paulo2951528676423035280This path
  4. Singapore29515286763389123673This path
  5. Oregon, US2951528676855142013This path

Each row is one path genuinely present in the routing table at our last snapshot, read outward from the origin to the vantage point that saw it. Open a row to follow that one path hop by hop. A heavier line in the graph means more vantage points reach the prefix that same way.

Route visibility

100%

Seen by 78 of 78 full-feed vantage points

Globally propagated

Observed at 5 of our collectors.

What this percentage counts

The denominator counts only full-feed peers — peers carrying a substantially complete routing table at the moment of the snapshot. IXP route-server peers usually feed partial tables and are excluded, because including them would make a normally propagated prefix look as though half the internet could not see it.

It measures how widely an announcement has spread across the networks we can observe. It says nothing about whether the prefix is reachable from any particular place, or how it performs.

Registry and RPKI

RIR
RIPE NCC — Europe, Middle East, Central Asia
Country
Germany
Allocated
8th April 1994
Allocation block
141.90.0.0/16
Status
assigned
Origin validation
No ROA

No ROA covers this prefix, so RPKI has nothing to say about it either way. This is still the common case for a large share of the routing table.

Prefix hierarchy

Announcements above, below and beside this one in the real routing table.

CoveringMore specific
Prefix hierarchy for 141.90.14.0/24: the announcements covering it on the left, the announcements inside it on the right. Every prefix drawn is also listed in the tables below.141.90.0.0/18AS29515141.90.14.0/24AS29515This prefix141.90.15.0/24AS29515

Left to right is specificity: a shorter mask covering more address space, then this prefix, then the announcements carved out inside it. Only the first few of each are drawn — the tables below list them all.

Covering announcements

Announcements that contain 141.90.14.0/24
PrefixAddressesOriginVisibility
141.90.0.0/1816.4kAS29515Hessische Zentrale fuer Datenverarbeitung78/78

More specific announcements

Nothing inside this block is announced separately.

Sibling prefixes

Prefixes of the same length sharing a parent block with 141.90.14.0/24
PrefixAddressesOriginVisibility
141.90.15.0/24256AS29515Hessische Zentrale fuer Datenverarbeitung78/78

History

  1. AS2951522nd October 2026 — present
  2. AS2054613th November 2026 — 14th November 2026
  3. AS2054621st October 2026 — 22nd October 2026
  4. AS2951512th October 2026 — 20th October 2026
  5. AS205466th October 2026 — 12th October 2026
  6. AS2951525th September 2026 — 6th October 2026
  7. AS2054629th September 2026 — 4th October 2026
  8. AS2054624th September 2026 — 25th September 2026
Why these dates start where they do

A first-seen date is the first time we saw that origin, not the first time it appeared in BGP. Our history is forward-only with no backfill, so it says nothing about the period before we started collecting — treat the earliest dates with suspicion.

Open 141.90.14.0/24 in the calculator/24 reference

Routing data derived from RouteViews MRT archives and public registry data.