Network report
Who holds an IP address, prefix or AS number, how it is routed (origin AS, RPKI, IRR), its reverse DNS, blocklist listings and PeeringDB record, with what to fix first.
Checking routing, RPKI, reverse DNS, blocklists and the registry. This usually takes 3 to 10 seconds.
Warning: AS35847 (AS-EFTL) announces 74 IPv4 and 19 IPv6 prefixes. 2 warnings
| AS page | AS35847 |
|---|---|
| Holder | AS-EFTL - Ezee Fiber |
| Allocation | ARIN, United States (US), assigned 2005-03-24 |
| Prefixes (IPv4 / IPv6) | 74 / 19 |
| RPKI valid | 97% (90 / 93) |
| Upstreams and peers | 12 |
| Peering policy | Open |
What to fix
-
Warning
3 of 93 announced prefixes have no ROA (RPKI not found): 192.159.37.0/24, 198.62.217.0/24, 198.62.218.0/23.
Without a ROA, networks cannot tell your routes from a hijack.
Fix: Create a ROA for each at your RIR portal, with origin AS35847 and a max length equal to the prefix length:
192.159.37.0/24 AS35847 max-length /24 198.62.217.0/24 AS35847 max-length /24 198.62.218.0/23 AS35847 max-length /23
-
Warning
65 of 93 announced prefixes have no IRR route object: 2606:a300:d::/48, 139.94.132.0/22, 170.203.114.0/23, 170.203.112.0/23, 2606:a300:b::/48 (+60).
Many networks build their prefix filters from IRR data; without route objects some of them drop the routes.
Fix: Create route (IPv4) and route6 (IPv6) objects with origin AS35847 in your RIR’s IRR database (or RADB).
route6: 2606:a300:d::/48 origin: AS35847 route: 139.94.132.0/22 origin: AS35847 route: 170.203.114.0/23 origin: AS35847
Checks
Routing and RPKI 3 of 93 announced prefixes have no ROA (RPKI not found): 192.159.37.0/24, 198.62.217.0/24, 198.62.218.0/23.
- Pass: AS35847 announces 74 IPv4 and 19 IPv6 prefixes.
- Warning: 3 of 93 announced prefixes have no ROA (RPKI not found): 192.159.37.0/24, 198.62.217.0/24, 198.62.218.0/23.
- Info: 90 of 93 announced prefixes are RPKI valid.
- Warning: 65 of 93 announced prefixes have no IRR route object: 2606:a300:d::/48, 139.94.132.0/22, 170.203.114.0/23, 170.203.112.0/23, 2606:a300:b::/48 (+60).
- Info: 12 upstreams and peers, 21 downstream networks seen.
| Holder | AS-EFTL - Ezee Fiber |
|---|---|
| IPv4 prefixes | 74 |
| IPv6 prefixes | 19 |
| RPKI | 90 valid · 3 not found |
| Without IRR route object | 65 |
| Downstream networks | 21 |
| Prefix | RPKI |
|---|---|
| 192.159.37.0/24 | No ROA |
| 198.62.217.0/24 | No ROA |
| 198.62.218.0/23 | No ROA |
Upstreams and peers seen to the left 12
Announced prefixes 93
Source: RIPEstat (RIPE NCC RIS, Routinator, IRR); AS names: Team Cymru
Open in ASN & BGP prefix lookupRegistration Found at rdap.arin.net.
- Pass: Found at rdap.arin.net.
| Name | AS-EFTL |
|---|---|
| Handle | AS35847 |
| Range | AS35847 |
| Status | active |
| Registered | 2005-03-24T13:58:43-05:00 |
| Last changed | 2024-03-20T12:47:52-04:00 |
| Abuse contact | noc@ezeefiber.com |
| Registry (RIR) | ARIN |
|---|---|
| Country | United States (US) |
| Delegated on | 2005-03-24 |
| Status | Assigned |
| Delegated range | AS35847 |
Source: RIR delegation data, updated daily. The country is where the range was registered, not necessarily where it is used.
| Role | Name | |
|---|---|---|
| registrant | Ezee Fiber |
Source: https://rdap.arin.net/registry/autnum/35847. Registration data from rdap.arin.net, shown under its terms of use (terms): not for marketing or bulk collection.
Open in WHOIS / RDAP lookupPeeringDB AS35847 is in PeeringDB as Ezee Fiber.
- Pass: AS35847 is in PeeringDB as Ezee Fiber.
- Info: Peering policy: Open.
- Info: Present at 9 internet exchanges with 9 ports (630G in total).
| Network | Ezee Fiber (Interfacing Company of Texas) |
|---|---|
| AS number | AS35847 |
| Type | Cable/DSL/ISP, Regional |
| Website | https://ezeefiber.com/ |
| IRR as-set | RADB::AS-ICTX |
| Prefixes (IPv4 / IPv6) | 500 / 50 |
| Traffic | 20-50Gbps, Mostly Inbound |
| Peering policy | Open |
| Locations | Not Required |
| Ratio required | No |
| Contracts | Not Required |
| Last updated | 2026-07-06 |
| NOC | noc@ezeefiber.com |
|---|
Source: PeeringDB. Results are cached for an hour.
Open in PeeringDB lookup