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

AS44851 ·

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

Warning: AS44851 (BG-RETEL-AS Retel JSC) announces 33 IPv4 and 2 IPv6 prefixes. 1 warning

AS pageAS44851
HolderBG-RETEL-AS Retel JSC
AllocationRIPE NCC, Bulgaria (BG), allocated 2008-03-20
Prefixes (IPv4 / IPv6)33 / 2
RPKI valid100% (35 / 35)
Upstreams and peers3

What to fix

  1. Warning

    PeeringDB did not answer: HTTP 404

    Fix: Try again in a minute.

    Open in PeeringDB lookup

Checks

Routing and RPKI AS44851 announces 33 IPv4 and 2 IPv6 prefixes.
  • Pass: AS44851 announces 33 IPv4 and 2 IPv6 prefixes.
  • Pass: All 35 announced prefixes are RPKI valid.
  • Pass: Every announced prefix has an IRR route object.
  • Info: 3 upstreams and peers, 2 downstream networks seen.
HolderBG-RETEL-AS Retel JSC
IPv4 prefixes33
IPv6 prefixes2
RPKI35 valid
Downstream networks2

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.
NameBG-RETEL-AS
HandleAS44851
RangeAS44851
Statusactive
Registered2008-03-20T09:11:41Z
Last changed2019-08-29T08:57:25Z
Abuse contactoffice@retelbg.com
Allocation
Registry (RIR)RIPE NCC
CountryBulgaria (BG)
Delegated on2008-03-20
StatusAllocated
Delegated rangeAS44851

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

Contacts
RoleNameEmail
registrant MNT-RETEL
registrant Retel JSC
registrant RIPE-NCC-END-MNT
abuse Abuse-C Role office@retelbg.com

Source: https://rdap.db.ripe.net/autnum/44851. 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