bgpreport

Network · data from 2026-11-12

AS48571 efectRO

Registry name: EFECTRO-As efectRO SRL, RO · PeeringDB

7IPv4 routes 85.7% RPKI valid · 85.7% with a route object
2IPv6 routes 50.0% RPKI valid · 50.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
2No ROA 2 with no route object for this origin
2Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS48571, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS48571, 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.
::/0 bogon No ROA None 0 0%low visibility 1
185.62.11.0/24 No ROA Other origin only 2 0%low visibility 2
81.181.168.0/23 Valid RIR databaseRIPE 673 100% 66
91.209.189.0/24 Valid RIR databaseRIPE 673 100% 66
91.216.80.0/24 Valid RIR databaseRIPE 673 100% 66
185.62.8.0/24 Valid RIR databaseRIPE 673 100% 66
194.55.152.0/22 Valid RIR databaseRIPE 673 100% 66
128.0.55.0/24 Valid RIR databaseRIPE 672 100% 66
2a0c:cb40::/29 Valid RIR databaseRIPE 635 100% 67

AS-SET

PeeringDB's irr_as_set for AS48571: RIPE::AS-EFECT. 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 (AS48571 isn't in the set, or no route object for AS48571 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 objectsAS48571 in itNot covered
RIPE::AS-EFECT RIPE 6113 Yes 2

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

  • Bogon prefix1
  • ROA: none1
  • Route object: none1
ChangePrefix or setDetailFull-table peers
Bogon prefix::/0In IANA's special-purpose registry: default route.0 of 636
ROA: none185.62.11.0/24No ROA covers it. Add a ROA for AS48571, maxLength 24.2 of 673
Route object: none185.62.11.0/24Route objects for it name AS834. Add a route object with origin AS48571 in the RIR database for the space.2 of 673

Route objects not announced

Every route object with origin AS48571 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.