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: AS5518 (TET_LV SIA Tet) announces 21 IPv4 and 2 IPv6 prefixes. 3 warnings
| AS page | AS5518 |
|---|---|
| Holder | TET_LV SIA Tet |
| Allocation | RIPE NCC, Latvia (LV), allocated 1996-01-16 |
| Prefixes (IPv4 / IPv6) | 21 / 2 |
| RPKI valid | 96% (22 / 23) |
| Upstreams and peers | 2 |
| Peering policy | No |
What to fix
-
Warning
1 of 23 announced prefixes have no ROA (RPKI not found): 91.231.68.0/24.
Without a ROA, networks cannot tell your routes from a hijack.
Fix: Create a ROA for each at your RIR portal, with origin AS5518 and a max length equal to the prefix length:
91.231.68.0/24 AS5518 max-length /24
-
Warning
9 of 23 announced prefixes have no IRR route object: 78.28.240.0/24, 2a02:16d8:104::/48, 78.28.244.0/24, 78.28.223.0/24, 80.233.146.0/24 (+4).
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 AS5518 in your RIR’s IRR database (or RADB).
route: 78.28.240.0/24 origin: AS5518 route6: 2a02:16d8:104::/48 origin: AS5518 route: 78.28.244.0/24 origin: AS5518
-
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 1 of 23 announced prefixes have no ROA (RPKI not found): 91.231.68.0/24.
- Pass: AS5518 announces 21 IPv4 and 2 IPv6 prefixes.
- Warning: 1 of 23 announced prefixes have no ROA (RPKI not found): 91.231.68.0/24.
- Info: 22 of 23 announced prefixes are RPKI valid.
- Warning: 9 of 23 announced prefixes have no IRR route object: 78.28.240.0/24, 2a02:16d8:104::/48, 78.28.244.0/24, 78.28.223.0/24, 80.233.146.0/24 (+4).
- Info: 2 upstreams and peers, 22 downstream networks seen.
| Holder | TET_LV SIA Tet |
|---|---|
| IPv4 prefixes | 21 |
| IPv6 prefixes | 2 |
| RPKI | 22 valid · 1 not found |
| Without IRR route object | 9 |
| Downstream networks | 22 |
| Prefix | RPKI |
|---|---|
| 91.231.68.0/24 | No ROA |
Upstreams and peers seen to the left 2
Announced prefixes 23
Source: RIPEstat (RIPE NCC RIS, Routinator, IRR); AS names: Team Cymru
Open in ASN & BGP prefix lookupRegistration Found at rdap.db.ripe.net.
- Pass: Found at rdap.db.ripe.net.
| Name | TET_LV |
|---|---|
| Handle | AS5518 |
| Range | AS5518 |
| Status | active |
| Registered | 2001-11-26T14:21:16Z |
| Last changed | 2024-11-27T14:19:30Z |
| Abuse contact | abuse@tet.lv |
| Registry (RIR) | RIPE NCC |
|---|---|
| Country | Latvia (LV) |
| Delegated on | 1996-01-16 |
| Status | Allocated |
| Delegated range | AS5518 |
Source: RIR delegation data, updated daily. The country is where the range was registered, not necessarily where it is used.
| Role | Name | |
|---|---|---|
| registrant | LTK | |
| registrant | SIA Tet | |
| registrant | RIPE-NCC-END-MNT | |
| registrant | TELIALV-MNT | |
| abuse | LTC Hostmaster | abuse@tet.lv |
Source: https://rdap.db.ripe.net/autnum/5518. 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 lookupPeeringDB No public NOC, policy or technical contact.
- Pass: AS5518 is in PeeringDB as Telia Latvija SIA.
- Info: Peering policy: No.
- Info: Present at 1 internet exchanges with 1 ports (10G in total).
- Warning: No public NOC, policy or technical contact.
| Network | Telia Latvija SIA |
|---|---|
| AS number | AS5518 |
| Type | , Not Disclosed |
| Website | http://telia.lv |
| IRR as-set | RIPE::AS-TELIANETLV |
| Prefixes (IPv4 / IPv6) | 0 / 0 |
| Traffic | Not Disclosed |
| Peering policy | No |
| Locations | Not Required |
| Ratio required | No |
| Contracts | Not Required |
| Last updated | 2026-11-02 |
Source: PeeringDB. Results are cached for an hour.
Open in PeeringDB lookup