77.91.90.0/24
At a glance
Addresses
/24 block
Visibility
80 of 80 vantage points
RPKI
Registry
MEAllocated 25th April 2007
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Singapore.
Seen from Singapore
- Peer of AS43581seen on 136 paths from 16 vantage points
- Peer of AS16262seen on 2,296 paths from 80 vantage points
- Peer of AS202984seen on 30,420 paths from 66 vantage points
- Peer of AS12389seen on 26,029 paths from 1 vantage point
- Peer of AS4766seen on 70,419 paths from 2 vantage points
RU
KR
SGOne 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
- London, UK4358148108622558529This path
- Amsterdam4358148108355986939213151This path
- Sao Paulo4358148108355986939266213This path
- Oregon, US435814810835598693920130This path
- Singapore4358116262202984123894766132337Shown 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
100%
Seen by 80 of 80 full-feed vantage points
Globally propagatedObserved 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
- Montenegro
- Allocated
- 25th April 2007
- Allocation block
- 77.91.80.0/20
- Status
- allocated
- Origin validation
- Valid
A ROA exists that authorises this origin AS to announce this prefix at this length.
ROAs covering this prefix
| ROA prefix | Authorised origin | Max length |
|---|---|---|
| 77.91.90.0/24 | AS43581 | /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
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 77.91.91.0/24 | 256 | AS48729ServerKing B.V. | 80/80 |
History
- AS4358112th 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 77.91.90.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.