SUBNET.IM

181.233.2.0/23

ZEUSNET TELECOMAS271339

At a glance

Addresses

512

/23 block

Visibility

100%

80 of 80 vantage points

RPKI

No ROA

Registry

LACNICBR

Allocated 8th December 2021

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 181.233.2.0/23, fanning out from AS271339 toward the vantage points that see it. Each path is written out in full beneath the graph.AS271339ZEUSNET TELECOMOriginAS262503WIKI TELECOMUNICA…AS266213PLANETCLICK TELEC…AS7195EdgeUnoAS8529Zain Omantel Inte…AS132337AxclusiveAS270735COMPUTIZE NETWORK…AS52320V.tal (GlobeNet)AS6939Hurricane Electri…AS213151Christian ElsenAS3257GTT Communication…AS23352DEFT.COMAS20130Depaul University
  1. Sao Paulo271339262503266213This path
  2. London, UK27133926250371958529This path
  3. Singapore2713392625037195132337This path
  4. Amsterdam271339262503270735523206939213151This path
  5. Oregon, US27133926250327073532572335220130This 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 80 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
LACNIC — Latin America and the Caribbean
Country
Brazil
Allocated
8th December 2021
Allocation block
181.233.0.0/22
Status
allocated
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 181.233.2.0/23: the announcements covering it on the left, the announcements inside it on the right. Every prefix drawn is also listed in the tables below.181.233.0.0/22AS271339181.233.2.0/23AS271339This prefix181.233.0.0/23AS271339181.233.2.0/24AS271339181.233.3.0/24AS271339

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 181.233.2.0/23
PrefixAddressesOriginVisibility
181.233.0.0/221kAS271339ZEUSNET TELECOM80/80

More specific announcements

Announcements contained within 181.233.2.0/23
PrefixAddressesOriginVisibility
181.233.2.0/24256AS271339ZEUSNET TELECOM80/80
181.233.3.0/24256AS271339ZEUSNET TELECOM80/80

Sibling prefixes

Prefixes of the same length sharing a parent block with 181.233.2.0/23
PrefixAddressesOriginVisibility
181.233.0.0/23512AS271339ZEUSNET TELECOM80/80

History

  1. AS27133912th 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 181.233.2.0/23 in the calculator/23 reference

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