bgpreport

Network · data from 2026-11-12

AS49418 netshield

Registry name: AS-NETSHIELD NETSHIELD LTD, GB · PeeringDB

13IPv4 routes 61.5% RPKI valid · 61.5% with a route object
5IPv6 routes 80.0% RPKI valid · 100.0% with a route object
5RPKI invalid 5 origin · 0 maxLength
1No ROA 5 with no route object for this origin
5Low visibility seen by under 10% of full-table peers
20Route objects not announced registered with origin AS49418, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS49418, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.

31.59.210.16/32 Invalid: origin None 1 0%low visibility 3
31.59.210.17/32 Invalid: origin None 1 0%low visibility 3
31.59.210.18/32 Invalid: origin None 1 0%low visibility 3
31.59.210.20/32 Invalid: origin None 1 0%low visibility 3
31.59.210.21/32 Invalid: origin None 1 0%low visibility 3
2a0f:cdc6:1005::/48 No ROA RIR databaseRIPE 632 99% 67
2.27.0.0/24 Valid RIR databaseRIPE 669 99% 66
64.188.127.0/24 Valid RIR databaseRIPE 669 99% 66
87.251.89.0/24 Valid RIR databaseRIPE 669 99% 67
89.169.14.0/24 Valid RIR databaseRIPE 669 99% 67
212.192.250.0/24 Valid RIR databaseRIPE 669 99% 67
212.192.255.0/24 Valid RIR databaseRIPE 669 99% 67
45.89.62.0/24 Valid RIR databaseRIPE 667 99% 67
64.188.114.0/24 Valid RIR databaseRIPE 667 99% 67
2a01:ecc0:10::/48 Valid RIR databaseRIPE 633 100% 69
2a01:ecc0:3::/48 Valid RIR databaseRIPE 632 99% 67
2a01:ecc0:4::/48 Valid RIR databaseRIPE 632 99% 67
2a01:ecc0:640::/42 Valid RIR databaseRIPE 632 99% 67

AS-SET

PeeringDB's irr_as_set for AS49418: RIPE::AS49418:AS-NETSHIELD. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS49418 isn't in the set, or no route object for AS49418 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS49418 in itNot covered
RIPE::AS49418:AS-NETSHIELD RIPE1 member set in no database: AS207567:AS-INTEZIO 4591,541 Yes 5

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 32 are in fix.csv.

  • ROA: origin5
  • ROA: none1
  • Route object: none5
  • AS-SET: missing member1
  • Route object: not announced20
ChangePrefix or setDetailFull-table peers
ROA: origin31.59.210.16/32ROAs covering it name AS197666, AS219506, not AS49418. If AS49418 should announce it, add a ROA for AS49418.1 of 673
Route object: none31.59.210.16/32No route object for it. Add a route object with origin AS49418 in the RIR database for the space.1 of 673
ROA: origin31.59.210.17/32ROAs covering it name AS197666, AS219506, not AS49418. If AS49418 should announce it, add a ROA for AS49418.1 of 673
Route object: none31.59.210.17/32No route object for it. Add a route object with origin AS49418 in the RIR database for the space.1 of 673
ROA: origin31.59.210.18/32ROAs covering it name AS197666, AS219506, not AS49418. If AS49418 should announce it, add a ROA for AS49418.1 of 673
Route object: none31.59.210.18/32No route object for it. Add a route object with origin AS49418 in the RIR database for the space.1 of 673
ROA: origin31.59.210.20/32ROAs covering it name AS197666, AS219506, not AS49418. If AS49418 should announce it, add a ROA for AS49418.1 of 673
Route object: none31.59.210.20/32No route object for it. Add a route object with origin AS49418 in the RIR database for the space.1 of 673
ROA: origin31.59.210.21/32ROAs covering it name AS197666, AS219506, not AS49418. If AS49418 should announce it, add a ROA for AS49418.1 of 673
Route object: none31.59.210.21/32No route object for it. Add a route object with origin AS49418 in the RIR database for the space.1 of 673
ROA: none2a0f:cdc6:1005::/48No ROA covers it. Add a ROA for AS49418, maxLength 48.632 of 636
AS-SET: missing memberRIPE::AS49418:AS-NETSHIELDAS49418:AS-NETSHIELD (RIPE) lists AS207567:AS-INTEZIO; no IRR database read has it.

Route objects not announced

Route objects with origin AS49418 whose prefix no peer sees AS49418 announce. Many are kept on purpose (backup routes, space announced only in some places).

2.27.2.0/24RIPEValid
62.95.0.0/16ALTDBNo ROA
90.96.0.0/15ALTDBNo ROA
145.6.0.0/15ALTDBNo ROA
185.218.137.0/24RIPEValid
193.233.86.0/24RIPEValid
194.153.135.0/24RIPEValid
2a01:ecc0:280::/42RIPEValid
2a01:ecc0:740::/42RIPEValid
2a0f:cdc6:45::/48RIPENo ROA
2a0f:cdc6:777::/48RIPENo ROA
2a0f:cdc6:1000::/48RIPENo ROA
2a0f:cdc6:1001::/48RIPENo ROA
2a0f:cdc6:1002::/48RIPENo ROA
2a0f:cdc6:1003::/48RIPENo ROA
2a0f:cdc6:1004::/48RIPENo ROA
2a0f:cdc6:1006::/48RIPENo ROA
2a0f:cdc6:1007::/48RIPENo ROA
2a0f:cdc6:1008::/48RIPENo ROA
2a0f:cdc6:1009::/48RIPENo ROA

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.