subnet.im

31.59.64.0/22

Pentech Bilisim Teknolojileri Sanayi Ve Ticaret Limited SirketiAS48678

At a glance

Addresses

1,024

/22 block

Visibility

6%

5 of 80 vantage points

RPKI

Invalid

Registry

RIPE NCCAE

Allocated 28th January 2011

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 31.59.64.0/22 as seen from Singapore, read outward from the origin: AS48678 → AS9121 → AS8966 → AS132337. Each hop is listed with its network name beneath the graph.AS48678Pentech Bilisim T…OriginAS9121Turk TelekomAS8966Etisalat (E&)AS132337Axclusive

Seen from Singapore

  1. 1AS48678Pentech Bilisim Teknolojileri Sanayi Ve Ticaret Limited SirketiTROrigin
    Peer of AS48678seen on 3,054 paths from 138 vantage points
  2. 2AS9121Turk TelekomTR
    Peer of AS9121seen on 987 paths from 1 vantage point
  3. 3AS8966Etisalat (E&)AE
    Peer of AS8966seen on 133,632 paths from 2 vantage points
  4. 4AS132337AxclusiveSGVantage 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. London, UK4867891218529This path
  2. Singapore4867891218966132337Shown 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. A heavier line in the graph means more vantage points reach the prefix that same way.

Route visibility

6%

Seen by 5 of 80 full-feed vantage points

Seen by few vantage points

Observed at 2 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
United Arab Emirates
Allocated
28th January 2011
Allocation block
31.56.0.0/14
Status
allocated
Origin validation
Invalid

A ROA covers this prefix but does not authorise this origin AS at this prefix length. That is either a misconfiguration or a hijack, and many networks will drop the route.

ROAs covering this prefix

Route Origin Authorisations covering 31.59.64.0/22
ROA prefixAuthorised originMax length
31.59.64.0/22AS0/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

No prefix of the same length in the same parent block is announced.

History

  1. AS4867812th 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 31.59.64.0/22 in the calculator/22 reference

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