AS46455
Transit ProviderNLI-AS46455
Also known as: JSI
6129 79th Street
4
IPv4 Prefixes
0
IPv6 Prefixes
1.0K
IPv4 Addresses
RIR
ARIN
Scope
Regional
Traffic
100-200Gbps
Ratio
Mostly Inbound
Peering
Selective
IRR AS-SET
AS-NLI
Risk Score
25/100
Network Characteristics
Unknown
IPv6 Enabled
宣告的前缀 (显示前 4 个)
| 前缀 | 网络类型 | 风险分 | 标签 | 首次发现 |
|---|---|---|---|---|
| 76.77.16.0/24 | transit | 25 |
-
|
2026-01-31 |
| 76.77.17.0/24 | transit | 25 |
-
|
2026-01-31 |
| 76.77.21.0/24 | transit | 25 |
-
|
2026-01-31 |
| 199.71.231.0/24 | transit | 25 |
-
|
2026-01-31 |
PeeringDB 备注
Network Lubbock is now JSI.
Contact Information
- Peering Requests & Inquiries: [email protected]
- 24x7 Network Operations Center (NOC): [email protected]
Contact Information
- Peering Requests & Inquiries: [email protected]
- 24x7 Network Operations Center (NOC): [email protected]
All networks are requested to keep their PeeringDB record accurate and up-to-date.
General Peering Requirements
All potential peering partners must meet the following criteria:
- Operate a 24x7 NOC that is responsive to operational and security issues.
- Maintain an accurate and complete PeeringDB entry, including NOC contact details and listed interconnection facilities.
- Maintain accurate route objects in a major Internet Routing Registry (IRR), such as RADb or ARIN. We will use this information to build prefix filters.
- Maintain accurate RPKI records.
- Must not point a default route or use static routes directed at our network for traffic that is not covered by the peering agreement.
- Must only announce your own prefixes and those of your direct downstream customers. We will not accept announcements for prefixes belonging to your transit providers or other peers.
- Must implement filtering to prevent the propagation of route leaks and bogon prefixes. We encourage the adoption of MANRS principles.
- Must agree to collaboratively troubleshoot and resolve network issues, including routing anomalies, security events, and performance degradation.
Public Peering (Internet Exchange Points - IXPs)
We welcome peering over shared IXP fabrics where we have a mutual presence.
- Locations: We are present at the following IXPs:
1. Equinix Dallas (DA3)
2. Amarillo Petroleum Building
- Requirements:
1. Both IPv4 and IPv6 sessions are required where available.
2. MD5 is not required but can be configured upon request.
Private Network Interconnect (PNI)
We will consider direct, private interconnections for networks that can exchange a significant volume of traffic with our network.
- Locations: We can establish PNIs at the following data centers:
1. 203 SW 8th Ave Amarillo, TX
2. 1950 Stemmons Dallas, TX
3. 1220 Broadway Lubbock, TX
- Requirements:
1. Peers are responsible for ordering and covering the costs of the physical cross-connect to our equipment in the mutual data center.
2. Link speeds supported are 10 Gbps and 100 Gbps.
Operational Policies
- Route Announcements: We will announce our aggregate prefixes and those of our downstream customers.
- Prefix Limits: We will set a maximum prefix limit based on the peer's IRR records. We request that peers do the same for our announcements. We will provide our suggested max-prefix value upon session establishment.
- Capacity Upgrades: We monitor all peering interface utilization. When an interface sustains traffic levels exceeding 75% for a 7-day period, we will initiate discussions with the peer to upgrade capacity. We expect our peers to have a similar policy.
- Maintenance: Scheduled maintenance will be announced at least 48 hours in advance via email to the peer's NOC contact. Emergency maintenance will be communicated as promptly as possible.
API 调用
# 使用 cURL 查询此 ASN
curl -H "Authorization: Bearer YOUR_API_KEY" \
"https://ipv4.dev/api/v1/asn/46455"