bgpreport

Network · data from 2026-11-12

AS57045 SpetsSvyaz AS57045

Registry name: NGS Panin Kirill Evgenyevich, RU · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS57045, 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.

91.230.65.0/24 No ROA RIR databaseRIPE 671 100% 66
91.221.43.0/24 Valid RIR databaseRIPE 673 100% 66
185.177.114.0/24 Valid RIR databaseRIPE 673 100% 66
80.76.41.0/24 Valid RIR databaseRIPE 672 100% 66
2a0e:1106:1000::/40 Valid RIR databaseRIPE 636 100% 67

AS-SET

PeeringDB's irr_as_set for AS57045: RIPE::AS-NGS. 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 (AS57045 isn't in the set, or no route object for AS57045 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 objectsAS57045 in itNot covered
RIPE::AS-NGS RIPE 21147 No 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 2 are in fix.csv.

  • ROA: none1
  • AS-SET: own ASN1
ChangePrefix or setDetailFull-table peers
ROA: none91.230.65.0/24No ROA covers it. Add a ROA for AS57045, maxLength 24.671 of 673
AS-SET: own ASNRIPE::AS-NGSAS57045 isn't in AS-NGS (RIPE) once expanded. Add AS57045 to it.

Route objects not announced

Every route object with origin AS57045 is announced.

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.