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: AS327786 (4G Telecom) announces 9 IPv4 and 1 IPv6 prefixes. 3 warnings
| AS page | AS327786 |
|---|---|
| Holder | 4G Telecom - 4G Telecom |
| Allocation | AFRINIC, South Sudan (SS), allocated 2014-08-29 |
| Prefixes (IPv4 / IPv6) | 9 / 1 |
| RPKI valid | 100% (10 / 10) |
| Upstreams and peers | 3 |
| Peering policy | Open |
What to fix
-
Warning
3 of 10 announced prefixes have no IRR route object: 38.43.72.0/24, 2c0f:6740::/32, 38.43.74.0/24.
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 AS327786 in your RIR’s IRR database (or RADB).
route: 38.43.72.0/24 origin: AS327786 route6: 2c0f:6740::/32 origin: AS327786 route: 38.43.74.0/24 origin: AS327786
-
Warning
No abuse contact is published for AS327786.
Other networks send reports of spam, attacks and hacked machines to the abuse contact. Without one, reports go nowhere and blocklists may list the whole range.
Fix: Add an abuse contact to the registration: abuse-c in the RIPE database, an Abuse POC at ARIN, an abuse mailbox (IRT) at APNIC, AFRINIC or LACNIC.
-
Warning
No public NOC, policy or technical contact.
Other networks use these addresses to set up peering and to reach you during an incident.
Fix: Add a role contact (for example noc@ or peering@ an address you monitor) with visibility Public.
Checks
Routing and RPKI 3 of 10 announced prefixes have no IRR route object: 38.43.72.0/24, 2c0f:6740::/32, 38.43.74.0/24.
- Pass: AS327786 announces 9 IPv4 and 1 IPv6 prefixes.
- Pass: All 10 announced prefixes are RPKI valid.
- Warning: 3 of 10 announced prefixes have no IRR route object: 38.43.72.0/24, 2c0f:6740::/32, 38.43.74.0/24.
- Info: 3 upstreams and peers, 3 downstream networks seen.
| Holder | 4G Telecom - 4G Telecom |
|---|---|
| IPv4 prefixes | 9 |
| IPv6 prefixes | 1 |
| RPKI | 10 valid |
| Without IRR route object | 3 |
| Downstream networks | 3 |
Upstreams and peers seen to the left 3
Source: RIPEstat (RIPE NCC RIS, Routinator, IRR); AS names: Team Cymru
Open in ASN & BGP prefix lookupRegistration No abuse contact is published for AS327786.
- Pass: Found at rdap.afrinic.net.
- Warning: No abuse contact is published for AS327786.
| Name | ORG-TA39-AFRINIC |
|---|---|
| Handle | AS327786 |
| Range | AS327786 |
| Status | active |
| Registered | 2014-08-29T08:40:00Z |
| Last changed | 2024-06-20T07:48:00Z |
| Registry (RIR) | AFRINIC |
|---|---|
| Country | South Sudan (SS) |
| Delegated on | 2014-08-29 |
| Status | Allocated |
| Delegated range | AS327786 |
Source: RIR delegation data, updated daily. The country is where the range was registered, not necessarily where it is used.
| Role | Name | |
|---|---|---|
| administrative, technical | Ala Rifaat | arifat@connect.com.ss |
| administrative | Dominic Fahed | dfahed@4gtelecom.net |
| technical | Ziad SARKIS | zsarkis@mymada.com |
| registrant | 4G Telecom | dfahed@4gtelecom.net |
Source: https://rdap.afrinic.net/rdap/autnum/327786. Registration data from rdap.afrinic.net, shown under its terms of use (terms): not for marketing or bulk collection.
Open in WHOIS / RDAP lookupPeeringDB No public NOC, policy or technical contact.
- Pass: AS327786 is in PeeringDB as 4G Telecom.
- Info: Peering policy: Open.
- Info: No internet exchange ports are listed.
- Warning: No public NOC, policy or technical contact.
| Network | 4G Telecom (Connect) |
|---|---|
| AS number | AS327786 |
| Type | Cable/DSL/ISP, Not Disclosed |
| Website | http://www.connect.com.ss |
| IRR as-set | AS-4GTELECOM |
| Prefixes (IPv4 / IPv6) | 15 / 2 |
| Traffic | 5-10Gbps, Not Disclosed |
| Peering policy | Open |
| Locations | Not Required |
| Ratio required | No |
| Contracts | Not Required |
| Last updated | 2025-01-29 |
Source: PeeringDB. Results are cached for an hour.
Open in PeeringDB lookup