Skip to content
thenetworkery

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.

IP address, prefix or AS number

AS20776 · 

curl -s "https://thenetworkery.com/api/v1/network-report?query=AS20776"
JSON Docs

Warning: AS20776 (OUTREMER-AS) announces 116 IPv4 and 0 IPv6 prefixes. 4 warnings

AS pageAS20776
HolderOUTREMER-AS Outremer Telecom SAS
AllocationRIPE NCC, Martinique (MQ), allocated 2001-05-25
Prefixes (IPv4 / IPv6)116 / 0
RPKI valid97% (112 / 116)
Upstreams and peers4

What to fix

  1. Warning

    No IPv6 prefixes announced.

    Networks without IPv6 force their users through NAT64 or leave them unreachable from IPv6-only networks.

    Fix: Get an IPv6 allocation from your RIR (usually free with your IPv4 membership) and announce it.

    Open in ASN & BGP prefix lookup

  2. Warning

    4 of 116 announced prefixes have no ROA (RPKI not found): 92.49.64.0/18, 93.176.32.0/19, 185.13.216.0/22, 185.13.216.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 AS20776 and a max length equal to the prefix length:

    92.49.64.0/18 AS20776 max-length /18
93.176.32.0/19 AS20776 max-length /19
185.13.216.0/22 AS20776 max-length /22
185.13.216.0/23 AS20776 max-length /23

    Open in RPKI / ROA validator Guide

  3. Warning

    109 of 116 announced prefixes have no IRR route object: 109.62.80.0/21, 217.175.172.0/24, 92.49.96.0/20, 109.62.16.0/21, 109.62.56.0/22 (+104).

    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 AS20776 in your RIR’s IRR database (or RADB).

    route: 109.62.80.0/21
origin: AS20776

route: 217.175.172.0/24
origin: AS20776

route: 92.49.96.0/20
origin: AS20776

    Open in ASN & BGP prefix lookup

  4. Warning

    PeeringDB did not answer: HTTP 404

    Fix: Try again in a minute.

    Open in PeeringDB lookup

Checks

Routing and RPKI No IPv6 prefixes announced.
  • Pass: AS20776 announces 116 IPv4 and 0 IPv6 prefixes.
  • Warning: No IPv6 prefixes announced.
  • Warning: 4 of 116 announced prefixes have no ROA (RPKI not found): 92.49.64.0/18, 93.176.32.0/19, 185.13.216.0/22, 185.13.216.0/23.
  • Info: 112 of 116 announced prefixes are RPKI valid.
  • Warning: 109 of 116 announced prefixes have no IRR route object: 109.62.80.0/21, 217.175.172.0/24, 92.49.96.0/20, 109.62.16.0/21, 109.62.56.0/22 (+104).
  • Info: 4 upstreams and peers, 3 downstream networks seen.
HolderOUTREMER-AS Outremer Telecom SAS
IPv4 prefixes116
IPv6 prefixes0
RPKI112 valid · 4 not found
Without IRR route object109
Downstream networks3
Routes to fix
PrefixRPKI
92.49.64.0/18 No ROA
93.176.32.0/19 No ROA
185.13.216.0/22 No ROA
185.13.216.0/23 No ROA

Upstreams and peers seen to the left 4

AS1299 Arelion (Twelve99) AS6762 Telecom Italia Sparkle AS21502 ASN-NUMERICABLE AS15557 SFR Group

Announced prefixes 116

80.243.240.0/20 80.243.240.0/21 80.243.248.0/21 82.197.96.0/19 82.197.96.0/20 82.197.112.0/20 89.3.240.0/21 89.3.248.0/21 89.16.0.0/19 89.16.0.0/20 89.16.0.0/21 89.16.8.0/21 89.16.16.0/20 89.16.16.0/21 89.16.24.0/21 89.157.88.0/21 92.49.64.0/18 92.49.64.0/19 92.49.64.0/20 92.49.80.0/20 92.49.96.0/19 92.49.96.0/20 92.49.96.0/21 92.49.104.0/21 92.49.104.0/24 92.49.105.0/24 92.49.106.0/24 92.49.107.0/24 92.49.108.0/22 92.49.112.0/20 92.49.112.0/21 92.49.120.0/21 92.49.125.0/24 93.176.0.0/19 93.176.0.0/20 93.176.16.0/20 93.176.32.0/19 93.176.32.0/20 93.176.48.0/20 109.62.0.0/17 109.62.0.0/19 109.62.0.0/21 109.62.4.0/22 109.62.8.0/24 109.62.9.0/24 109.62.10.0/23 109.62.12.0/23 109.62.14.0/24 109.62.15.0/24 109.62.16.0/21 109.62.24.0/23 109.62.26.0/24 109.62.27.0/24 109.62.28.0/22 109.62.32.0/20 109.62.48.0/20 109.62.48.0/21 109.62.56.0/22 109.62.60.0/22 109.62.64.0/23 109.62.64.0/24 109.62.65.0/24 109.62.66.0/23 109.62.66.0/24 109.62.67.0/24 109.62.68.0/22 109.62.68.0/23 109.62.70.0/23 109.62.72.0/21 109.62.72.0/22 109.62.76.0/22 109.62.80.0/20 109.62.80.0/21 109.62.88.0/21 109.62.96.0/20 109.62.96.0/21 109.62.104.0/21 109.62.112.0/21 109.62.120.0/21 109.203.224.0/20 109.203.240.0/20 185.13.216.0/22 185.13.216.0/23 185.13.218.0/23 188.115.64.0/18 188.115.64.0/19 188.115.64.0/20 188.115.80.0/20 188.115.96.0/19 188.115.96.0/21 188.115.104.0/21 188.115.112.0/20 212.198.242.0/23 212.198.242.0/24 212.198.243.0/24 212.198.254.0/23 212.198.254.0/24 212.198.255.0/24 217.175.160.0/19 217.175.160.0/24

Showing the first 100.

Source: RIPEstat (RIPE NCC RIS, Routinator, IRR); AS names: Team Cymru

Open in ASN & BGP prefix lookup
Registration Found at rdap.db.ripe.net.
  • Pass: Found at rdap.db.ripe.net.
NameOUTREMER-AS
HandleAS20776
RangeAS20776
Statusactive
Registered2002-07-04T17:12:41Z
Last changed2024-09-04T12:43:22Z
Abuse contactripe@outremer-telecom.fr
Allocation
Registry (RIR)RIPE NCC
CountryMartinique (MQ)
Delegated on2001-05-25
StatusAllocated
Delegated rangeAS20776

Source: RIR delegation data, updated daily. The country is where the range was registered, not necessarily where it is used.

Contacts
RoleNameEmail
registrant Outremer Telecom SAS
registrant OUTREMER-MNT
registrant RIPE-NCC-END-MNT
abuse Abuse-C Role ripe@outremer-telecom.fr

Source: https://rdap.db.ripe.net/autnum/20776. Registration data from rdap.db.ripe.net, shown under its terms of use (terms): not for marketing or bulk collection. Personal contacts in this registry are not shown.

Open in WHOIS / RDAP lookup
PeeringDB PeeringDB did not answer: HTTP 404
  • Warning: PeeringDB did not answer: HTTP 404

Source: PeeringDB. Results are cached for an hour.

Open in PeeringDB lookup