subnet.im

193.223.253.0/24

At a glance

Addresses

256

/24 block

Visibility

5%

4 of 80 vantage points

RPKI

Valid

Registry

RIPE NCCPS

Allocated 16th October 2019

AS paths to this prefix

All paths

One observed path, hop by hop, from the origin out to Singapore.

OriginVantage point · Singapore
One AS path to 193.223.253.0/24 as seen from Singapore, read outward from the origin: AS29310 → AS12975 → AS8697 → AS15802 → AS8966 → AS132337. Each hop is listed with its network name beneath the graph.AS29310JAWWALOriginAS12975Palestine Telecom…AS8697Jordan Telecommun…AS15802Emirates Integrat…AS8966Etisalat (E&)AS132337Axclusive

Seen from Singapore

  1. 1AS29310JAWWALPSOrigin
    Peer of AS29310seen on 798 paths from 79 vantage points
  2. Peer of AS12975seen on 1,201 paths from 9 vantage points
  3. Peer of AS8697seen on 1,196 paths from 4 vantage points
  4. Peer of AS15802seen on 16,292 paths from 87 vantage points
  5. Peer of AS8966seen on 133,632 paths from 2 vantage points
  6. 6AS132337AxclusiveSGVantage point

One path, hop by hop, from the origin outward to the vantage point that saw it. Counts beside each step are how often we see that pair adjacent anywhere in the table, not how often this path was used — BGP carries no traffic figures.

Every path we see

  1. Singapore29310129758697158028966132337Shown above

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.

Route visibility

5%

Seen by 4 of 80 full-feed vantage points

Seen by few vantage points

Observed at 1 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
Palestinian Territories
Allocated
16th October 2019
Allocation block
193.223.252.0/23
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 193.223.253.0/24
ROA prefixAuthorised originMax length
193.223.252.0/23AS12975/24
193.223.252.0/23AS19905/24
193.223.252.0/23AS29310/24

Prefix hierarchy

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

Covering announcements

No less specific announcement covers this prefix.

More specific announcements

Nothing inside this block is announced separately.

Sibling prefixes

Prefixes of the same length sharing a parent block with 193.223.253.0/24
PrefixAddressesOriginVisibility
193.223.252.0/24256AS29310JAWWAL4/80

History

  1. AS2931012th 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 193.223.253.0/24 in the calculator/24 reference

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