How can I access the full ASN tables?

The page shows a preview of large ASN datasets. Use the page controls to load more rows, and upgrade to a paid plan for complete access.

AS46445 TELPAGE | IPGeolocation.io

Q: Why is WHOIS data shown for an ASN?

WHOIS data provides registration and contact context for ASN ownership, administration, and operational reference.

ASN Lookup Tool

TELPAGE telpage.net

US 1 Routes

AS Data

AS46445

AS46445 – TELPAGE

AS Number	46445
AS Name	TELPAGE-EMP
Organization	TELPAGE (telpa)
Country	US
Website	telpage.net
Number of IPv4 Routes	1
Number of IPv6 Routes	0
ASN type	ISP
Registry	ARIN
Date Allocated	2012-11-19

ASN Intelligence API for production workflows

Use ASN data for AS46445 in automation: routing intelligence, peering analysis, ownership checks, and network observability.

Access complete peers, upstreams, downstreams, routes, WHOIS, and contact intelligence via our API. Learn more

Get ASN API Key ASN API Docs

IP Ranges

Route	Origin	Origin Name	ISP	# IPs
192.40.120.0/21	AS46445	TELPAGE	TELPAGE	2048

Raw Whois Response

#
# 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:       46445
ASName:         TELPAGE-EMP
ASHandle:       AS46445
RegDate:        2012-11-19
Updated:        2012-11-19
Ref:            https://rdap.arin.net/registry/autnum/46445


OrgName:        TELPAGE
OrgId:          TELPA
Address:        636 SOUTH MAIN STREET
City:           EMPORIA
StateProv:      VA
PostalCode:     23847
Country:        US
RegDate:        2004-03-29
Updated:        2024-11-25
Ref:            https://rdap.arin.net/registry/entity/TELPA


OrgTechHandle: GRIGG5-ARIN
OrgTechName:   Grigg, Charles 
OrgTechPhone:  +1-434-634-6100 
OrgTechEmail:  cgrigg@telpage.net
OrgTechRef:    https://rdap.arin.net/registry/entity/GRIGG5-ARIN

OrgAbuseHandle: SKG5-ARIN
OrgAbuseName:   Grigg, Susan K
OrgAbusePhone:  +1-434-634-5100 
OrgAbuseEmail:  sgrigg@telpage.net
OrgAbuseRef:    https://rdap.arin.net/registry/entity/SKG5-ARIN

OrgAbuseHandle: GRIGG5-ARIN
OrgAbuseName:   Grigg, Charles 
OrgAbusePhone:  +1-434-634-6100 
OrgAbuseEmail:  cgrigg@telpage.net
OrgAbuseRef:    https://rdap.arin.net/registry/entity/GRIGG5-ARIN

OrgTechHandle: HORNE13-ARIN
OrgTechName:   Horne, Meade 
OrgTechPhone:  +1-434-634-5100 
OrgTechEmail:  hornem@telpage.net
OrgTechRef:    https://rdap.arin.net/registry/entity/HORNE13-ARIN

OrgNOCHandle: HORNE13-ARIN
OrgNOCName:   Horne, Meade 
OrgNOCPhone:  +1-434-634-5100 
OrgNOCEmail:  hornem@telpage.net
OrgNOCRef:    https://rdap.arin.net/registry/entity/HORNE13-ARIN

OrgNOCHandle: GRIGG5-ARIN
OrgNOCName:   Grigg, Charles 
OrgNOCPhone:  +1-434-634-6100 
OrgNOCEmail:  cgrigg@telpage.net
OrgNOCRef:    https://rdap.arin.net/registry/entity/GRIGG5-ARIN


#
# 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.
#

Parsed Whois Response

{
  "status" : true,
  "whois_server" : "whois.arin.net",
  "aut_nums" : [ {
    "aut_num" : "46445",
    "as_handle" : "AS46445",
    "as_name" : "TELPAGE-EMP",
    "tech_contacts" : [ "GRIGG5-ARIN", "HORNE13-ARIN" ],
    "abuse_contacts" : [ "SKG5-ARIN", "GRIGG5-ARIN" ],
    "date_created" : "2012-11-19",
    "date_updated" : "2012-11-19",
    "source" : "https://rdap.arin.net/registry/autnum/46445"
  } ],
  "organization" : {
    "handle" : "TELPA",
    "name" : "TELPAGE",
    "address" : [ "636 SOUTH MAIN STREET", "EMPORIA", "VA", "23847", "US" ],
    "street" : "South Main Street",
    "city" : "Emporia",
    "state" : "VA",
    "zip_code" : "23847",
    "country" : [ "US" ],
    "date_created" : "2004-03-29",
    "date_updated" : "2024-11-25",
    "source" : "https://rdap.arin.net/registry/entity/TELPA",
    "addressCountry" : "US"
  },
  "technical_contacts" : [ {
    "handle" : "GRIGG5-ARIN",
    "name" : "Grigg, Charles",
    "email" : [ "cgrigg@telpage.net" ],
    "phone" : [ "+1-434-634-6100" ],
    "source" : "https://rdap.arin.net/registry/entity/GRIGG5-ARIN"
  }, {
    "handle" : "HORNE13-ARIN",
    "name" : "Horne, Meade",
    "email" : [ "hornem@telpage.net" ],
    "phone" : [ "+1-434-634-5100" ],
    "source" : "https://rdap.arin.net/registry/entity/HORNE13-ARIN"
  } ],
  "abuse_contacts" : [ {
    "handle" : "SKG5-ARIN",
    "name" : "Grigg, Susan K",
    "email" : [ "sgrigg@telpage.net" ],
    "phone" : [ "+1-434-634-5100" ],
    "source" : "https://rdap.arin.net/registry/entity/SKG5-ARIN"
  }, {
    "handle" : "GRIGG5-ARIN",
    "name" : "Grigg, Charles",
    "email" : [ "cgrigg@telpage.net" ],
    "phone" : [ "+1-434-634-6100" ],
    "source" : "https://rdap.arin.net/registry/entity/GRIGG5-ARIN"
  } ]
}

Peers

AS Number	Description	Country
AS32425	Pixel Factory	US

Upstreams

AS Number	Description	Country
AS32425	Pixel Factory	US

Frequently Asked Questions

What is ASN AS46445?

ASN AS46445 is an Autonomous System Number used to identify a network for BGP internet routing.

Who manages ASN AS46445?

AS46445 is listed under TELPAGE.

What do peers, upstreams, and downstreams mean?

Peers are lateral network interconnections, upstreams are transit providers, and downstreams are customer networks receiving connectivity.

What are routes and IP ranges for an ASN?

Routes and IP ranges are the network prefixes announced by the ASN on the internet and show the address space it originates.

Why is WHOIS data included here?

WHOIS provides registration and contact context for ASN ownership, administration, and operational reference.

How can I access full ASN table data?

This page previews large ASN datasets. Use See more to load additional rows, and upgrade your plan to view complete peer, route, upstream, and downstream data.