bgpreport

Network · data from 2026-11-12

AS62553 Elcro Digital Group

Registry name: ELCRO-DIGITAL-SERVICES-LLC - Elcro Digital Services, LLC, US · PeeringDB

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

Announced routes

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

213.145.83.0/24 Valid RIR databaseRADB, RIPE 671 100% 66
216.109.178.0/24 Valid RIR databaseARIN 669 99% 67
216.109.176.0/24 Valid RIR databaseARIN 2 0%low visibility 1

AS-SET

PeeringDB's irr_as_set for AS62553: AS-EDAS. 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 (AS62553 isn't in the set, or no route object for AS62553 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 objectsAS62553 in itNot covered
AS-EDAS ARINlists itself further down4 member sets in no database: AS-MOTP, AS-ROUTE48, AS199746:AS-NEXTSERV, AS203867:AS-CUSTOMERS 1,00236723,700 Yes 0

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 20 are in fix.csv.

  • AS-SET: missing member4
  • Route object: not announced16
ChangePrefix or setDetailFull-table peers
AS-SET: missing memberAS-EDASAS-EDAS (ARIN) lists AS-MOTP; no IRR database read has it.
AS-SET: missing memberAS-EDASAS-EDAS (ARIN) lists AS-ROUTE48; no IRR database read has it.
AS-SET: missing memberAS-EDASAS-EDAS (ARIN) lists AS199746:AS-NEXTSERV; no IRR database read has it.
AS-SET: missing memberAS-EDASAS-EDAS (ARIN) lists AS203867:AS-CUSTOMERS; no IRR database read has it.

Route objects not announced

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

5.56.24.0/24RADB, RIPEValid
23.129.100.0/24ARINValid
23.167.232.0/24ARINValid
65.216.164.0/24RADBNo ROA
130.12.156.0/24ARINInvalid: origin
142.248.45.0/24ARINValid
162.216.176.0/22RADBNo ROA
216.109.176.0/22ARINValid
216.109.179.0/24ARINValid
2602:f71e::/40ARINValid
2602:f71e:41::/48ARINValid
2602:f71e:72::/48ARINValid
2602:f71e:80::/44ARINValid
2602:f71e:200::/40ARINValid
2602:fa11:10::/44ARINNo ROA
2602:ffe5:4::/48RADBNo 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.