Summary

  • AS36049 remains registered in ARIN under OrgID JABWI, whose registered name is JAB Wireless, INC. of Englewood, Colorado; the AS object carries a 2015-05-18 date while the organisation object carries 2025-08-15.
  • The last observed announcement for AS36049 was 208.95.16.0/22 on 11 December 2018, with 0 of 326 RIS peers seeing IPv4 announcements and announced_space 0 in the routing status record.
  • The registry object and the route table therefore describe two different things: the first is an administrative identifier that persists until someone acts on it, the second is an operational state that ended years ago.

What the registry still holds

The Autonomous System number 36049 is an object in the ARIN registry. The AS object itself is dated 2015-05-18, while the organisation object behind it, OrgID JABWI, is dated 2025-08-15. The registrant name on the AS record is Virtela, and the organisation name on the org record is JAB Wireless, INC., with an Englewood, Colorado address. The AS record is public in bgp.tools' AS36049 view and the registry relationship is visible through RIPE Stat's routing status endpoint for AS36049.

The dates matter because they are not the same date. An AS object dated 2015-05-18 and an organisation object dated 2025-08-15 describe two layers of the same registration that have been touched at different times. The organisation object was updated in August 2025; the AS object's date reflects its own last change. Anyone treating an AS number as a single dated fact is collapsing two records into one.

What the routing table last saw

RIPE Stat's routing status for AS36049 records the last observed announcement as 208.95.16.0/22 on 2018-12-11. In the same record, 0 of 326 RIS peers observed IPv4 announcements from this AS, and announced_space is 0. That is not a partial withdrawal or a thin presence; it is an AS number with no observed IPv4 announcements in the RIS view.

The prefix involved, 208.95.16.0/22, sits in a block whose registry lineage traces to ARIN space. The point for operators is that the withdrawal happened at the routing layer only. Withdrawing a prefix changes what the global table carries. It does not remove the AS number, the organisation object, or the association between them from the registry.

A different name in the operator-facing layer

PeeringDB's record for the same AS number lists the organisation as Rise Internet, with the alias JAB Wireless TX, at Digital Realty's DFW facility. That is a third naming layer on top of the two registry records. The PeeringDB ASN listing presents the network-facing identity that peers use when deciding whether and where to interconnect, and it does not read as Virtela.

So three public surfaces describe AS36049 in three ways: the ARIN AS object says Virtela, the ARIN organisation object says JAB Wireless, INC., and the PeeringDB organisation says Rise Internet with a JAB Wireless TX alias. None of these is wrong. They are different records maintained for different purposes, updated on different schedules, and read by different audiences.

Why the identifier survives

The survival of AS36049 after its routing went quiet is not a registry failure. Registries are designed to hold allocations and assignments; they are not designed to delete an identifier when the holder stops announcing routes. The registry records who is entitled to use a number resource. The route table records who is actually using it. The two systems are coupled only when a holder acts, and the default state of the registry is persistence.

That has practical consequences in both directions. An AS number that is registered but unrouted is still a nameable object in whois and registry lookups; it can appear in analyses, procurement discussions and due-diligence checks long after the network it was registered for has changed hands or changed purpose. Conversely, a network that is actively announcing routes under a given AS number may be doing so under a registry record whose registrant name no longer matches how the operator presents itself to peers.

For anyone assessing an AS number as an asset, the implication is that registry presence and operational presence are separate tests. The first test is administrative: does an AS object exist, who is the registered holder, and when was the record last touched. The second test is operational: is the AS number announcing prefixes now, to whom, and how widely observed is that announcement. AS36049 passes the first test and fails the second.

What this case does not establish

This account rests on public registry and routing observations and does not establish why AS36049 stopped announcing, whether the number resource has been transferred, leased or repurposed since 2018, or what contractual relationship, if any, exists between the registry registrant and the organisation named in the operator-facing layer. The RIPE Stat record shows a routing state; the ARIN records show registration state; neither is a title document.

The dates also carry a limit. An organisation object dated 2025-08-15 shows when that record was last changed, not when the underlying corporate fact changed. A change to an org record may reflect an administrative update, a contact change or a name correction. Reading the 2025-08-15 date as the date a company changed hands would be an inference the evidence does not support.