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

AS43515 ·

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

Problem: AS43515 (YOUTUBE) announces 193 IPv4 and 39 IPv6 prefixes. 1 problem · 2 warnings

AS pageAS43515
HolderYOUTUBE Google Ireland Limited
AllocationRIPE NCC, Ireland (IE), allocated 2007-08-15
Prefixes (IPv4 / IPv6)193 / 39
RPKI valid98% (228 / 232)
Upstreams and peers10
Peering policyRestrictive

What to fix

  1. Problem

    4 of 232 announced prefixes are RPKI invalid: 57.140.198.0/24, 57.140.201.0/24, 57.140.208.0/24, 57.140.212.0/24.

    A ROA covers them but does not allow this origin or prefix length, so networks that filter (most large ones do) drop these routes.

    Fix: Fix the ROAs (origin AS and max length) at your RIR, or stop announcing the routes.

    Open in RPKI / ROA validator Guide

  2. Warning

    1 of 232 announced prefixes have no IRR route object: 57.140.198.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 AS43515 in your RIR’s IRR database (or RADB).

    route: 57.140.198.0/24
    origin: AS43515

    Open in ASN & BGP prefix lookup

  3. 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.

    Open in PeeringDB lookup

Checks

Routing and RPKI 4 of 232 announced prefixes are RPKI invalid: 57.140.198.0/24, 57.140.201.0/24, 57.140.208.0/24, 57.140.212.0/24.
  • Pass: AS43515 announces 193 IPv4 and 39 IPv6 prefixes.
  • Problem: 4 of 232 announced prefixes are RPKI invalid: 57.140.198.0/24, 57.140.201.0/24, 57.140.208.0/24, 57.140.212.0/24.
  • Info: 228 of 232 announced prefixes are RPKI valid.
  • Warning: 1 of 232 announced prefixes have no IRR route object: 57.140.198.0/24.
  • Info: 10 upstreams and peers, 1 downstream networks seen.
HolderYOUTUBE Google Ireland Limited
IPv4 prefixes193
IPv6 prefixes39
RPKI228 valid · 4 invalid
Without IRR route object1
Downstream networks1
Routes to fix
PrefixRPKI
57.140.198.0/24 RPKI invalid
57.140.201.0/24 RPKI invalid
57.140.208.0/24 RPKI invalid
57.140.212.0/24 RPKI invalid

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.
NameYOUTUBE
HandleAS43515
RangeAS43515
Statusactive
Registered2007-08-15T07:35:37Z
Last changed2018-09-04T10:26:13Z
Abuse contactripe-contact@google.com
Allocation
Registry (RIR)RIPE NCC
CountryIreland (IE)
Delegated on2007-08-15
StatusAllocated
Delegated rangeAS43515

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

Contacts
RoleNameEmail
registrant MNT-YOU-TUBE
registrant Google Ireland Limited
registrant RIPE-NCC-END-MNT
abuse Abuse-C Role ripe-contact@google.com

Source: https://rdap.db.ripe.net/autnum/43515. 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 No public NOC, policy or technical contact.
  • Pass: AS43515 is in PeeringDB as Google LLC AS43515.
  • Info: Peering policy: Restrictive.
  • Info: No internet exchange ports are listed.
  • Warning: No public NOC, policy or technical contact.
NetworkGoogle LLC AS43515
AS numberAS43515
TypeContent, Global
Websitehttp://www.google.com
IRR as-setRADB::AS-43515-YT
Prefixes (IPv4 / IPv6)0 / 0
TrafficHeavy Outbound
Peering policyRestrictive
LocationsNot Required
Ratio requiredNo
ContractsNot Required
Last updated2026-01-22

Source: PeeringDB. Results are cached for an hour.

Open in PeeringDB lookup