SUBNET.IM

45.219.0.0/17

Orange MarocAS36925

At a glance

Addresses

32,768

/17 block

Visibility

99%

79 of 80 vantage points

RPKI

Valid

Registry

AFRINICMA

Allocated 24th February 2015

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 45.219.0.0/17, fanning out from AS36925 toward the vantage points that see it. Each path is written out in full beneath the graph.AS36925Orange MarocOriginAS174Cogent Communicat…AS132337AxclusiveAS34549meerfarbig GmbH &…AS213151Christian ElsenAS1299Arelion (fka. Tel…AS8529Zain Omantel Inte…AS3356Lumen (Level 3)AS266213PLANETCLICK TELEC…AS5511Orange S.A.AS6939Hurricane Electri…AS20130Depaul University
  1. Singapore36925174132337This path
  2. Amsterdam3692517434549213151This path
  3. London, UK3692517412998529This path
  4. Sao Paulo369251743356266213This path
  5. Oregon, US369255511693920130This 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

99%

Seen by 79 of 80 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
AFRINIC — Africa
Country
Morocco
Allocated
24th February 2015
Allocation block
45.216.0.0/14
Status
allocated
Origin validation
Valid

A ROA exists that authorises this origin AS to announce this prefix at this length.

ROAs covering this prefix

Route Origin Authorisations covering 45.219.0.0/17
ROA prefixAuthorised originMax length
45.216.0.0/14AS36925/24

Prefix hierarchy

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

CoveringMore specific
Prefix hierarchy for 45.219.0.0/17: the announcements covering it on the left, the announcements inside it on the right. Every prefix drawn is also listed in the tables below.45.219.0.0/16AS3692545.218.0.0/15AS3692545.216.0.0/14AS3692545.219.0.0/17AS36925This prefix45.219.128.0/17AS3692545.219.0.0/18AS3692545.219.64.0/18AS36925

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 45.219.0.0/17
PrefixAddressesOriginVisibility
45.219.0.0/1665.5kAS36925Orange Maroc79/80
45.218.0.0/15131kAS36925Orange Maroc79/80
45.216.0.0/14262kAS36925Orange Maroc79/80

More specific announcements

Announcements contained within 45.219.0.0/17
PrefixAddressesOriginVisibility
45.219.0.0/1816.4kAS36925Orange Maroc79/80
45.219.64.0/1816.4kAS36925Orange Maroc80/80

Sibling prefixes

Prefixes of the same length sharing a parent block with 45.219.0.0/17
PrefixAddressesOriginVisibility
45.219.128.0/1732.8kAS36925Orange Maroc79/80

History

  1. AS3692512th August 2026 — present
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 45.219.0.0/17 in the calculator/17 reference

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