AS46997 Black Mesa Corporation
AS46997 (NATOLAB) is registered to Black Mesa Corporation in US, through ARIN. It originates 38 prefixes in the global routing table.
Who holds AS46997
Names from RIPE NCC’s daily list of every allocated AS number. The ASN lookup fetches the full WHOIS record live.
WHOIS recordARIN
#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/resources/registry/whois/tou/
#
# If you see inaccuracies in the results, please report at
# https://www.arin.net/resources/registry/whois/inaccuracy_reporting/
#
# Copyright 1997-2026, American Registry for Internet Numbers, Ltd.
#
ASNumber: 46997
ASName: NATOLAB
ASHandle: AS46997
RegDate: 2020-05-04
Updated: 2020-09-19
Comment: use the following communities to control route export:
Comment:
Comment: IX peer export
Comment: --------------
Comment:
Comment: 46997:100XY
Comment: where X := {
Comment: 1 = SIX,
Comment: 2 = KleyReX,
Comment: 3 = LocIX Frankfurt,
Comment: 4 = Unmetered Exchange
Comment: }, Y := {
Comment: 0 = do not announce,
Comment: 1 = prepend 1x,
Comment: 2 = prepend 2x,
Comment: 3 = prepend 3x
Comment: }
Comment:
Comment: example: do not export to KleyReX: 46997:10020
Comment:
Comment: local preference
Comment: ----------------
Comment:
Comment: 46997:1010X
Comment: where X := {
Comment: 0 = local_pref 0, # lowest
Comment: 1 = local_pref 20, # transit
Comment: 2 = local_pref 40, # ix peering
Comment: 3 = local_pref 100, # default customer
Comment: 4 = local_pref 110, # higher than default customer
Comment: }
Comment:
Comment: example: set local_pref 0: 46997:10100
Comment:
Comment: upstream export
Comment: ---------------
Comment:
Comment: 46997:102XY
Comment: where X := {
Comment: 0 = AS6939, # Hurricane Electric
Comment: 1 = AS29632, # Netassist
Comment: 2 = AS39533, # Asympto Networks
Comment: 3 = AS201106, # Spartan Host
Comment: 4 = AS38008, # Aperture Science
Comment: 5 = AS206499, # M&M Networks
Comment: 6 = AS20473, # Choopa
Comment: 7 = AS41051, # Openfactory
Comment: 8 = AS54133, # Unmetered Internet
Comment: 9 = AS34927 # iFog
Comment: }, Y := {
Comment: 0 = do not announce,
Comment: 1 = prepend 1x,
Comment: 2 = prepend 2x,
Comment: 3 = prepend 3x
Comment: }
Comment:
Comment: example: do not export to Aperture Science: 46997:10240
Comment:
Comment: options
Comment: -------
Comment:
Comment: 46997:46997 enable anycast
Comment:
Comment:
Comment: as46997 tags routes with the following communities:
Comment:
Comment: prefix source
Comment: -------------
Comment:
Comment: 46997:100X
Comment: where X := {
Comment: 0 = originated by as46997,
Comment: 1 = learned from upstream,
Comment: 2 = learned from private peering
Comment: 3 = learned from IX peering,
Comment: 4 = learned from customer
Comment: }
Comment:
Comment: prefix PoP
Comment: ----------
Comment:
Comment: 46997:10X (prefix PoP)
Comment: where X := {
Comment: 0 = Seattle,
Comment: 1 = Matawan,
Comment: 2 = Frankfurt,
Comment: 3 = Tokyo,
Comment: 4 = Guangzhou,
Comment: 5 = Fremont,
Comment: 6 = Hongkong,
Comment: What AS46997 announces
Prefixes originated by AS46997 in the RouteViews table (refreshed every four hours), each checked against the RPKI (every ten minutes) and the IRR (daily).
Announced prefixes
Each opens its own page: who announces it, the paths our collectors see, its ROAs and route objects.
RPKI valid RPKI invalid no ROA covers it
Who AS46997 is reached through
The AS just before AS46997 in the paths our looking glass collectors hold, for 38 of its prefixes. Usually a transit provider, sometimes a peer. The number is how many of those prefixes it was seen on.
Provider authorization
AS46997 publishes no ASPA of its own. 1 AS name it as a provider in theirs. Check a path.
The 1 ASes that name AS46997 as a provider
Routing registry objects
From the mirrored IRR databases (RADB, the five RIRs and more). Look it up live.
| Source | as-name | Maintained by |
|---|---|---|
| ARIN | NATOLAB-2 | MNT-NRL-25 |
Route objects with origin AS46997: ARIN 22 · ALTDB 12 · APNIC 11 · RADB 7