bgpreport

Network · data from 2026-11-12

AS267224 LOGPLAY - Itelecom Solucoes Em Comunicacoes LTDA

Registry name: AS267224 - SIGA FIBRA LTDA, BR · PeeringDB

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

Announced routes

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

45.231.193.0/24 Valid Nonecovered by 45.231.192.0/23 670 100% 67
45.231.194.0/24 Valid Nonecovered by 45.231.194.0/23 670 100% 67
45.231.195.0/24 Valid Nonecovered by 45.231.194.0/23 668 99% 67
2804:4a34::/33 Valid Nonecovered by 2804:4a34::/32 636 100% 67
2804:4a34::/34 Valid Nonecovered by 2804:4a34::/32 636 100% 67
2804:4a34:1000::/48 Valid Nonecovered by 2804:4a34::/32 636 100% 67
2804:4a34:1001::/48 Valid Nonecovered by 2804:4a34::/32 636 100% 67
2804:4a34:4000::/34 Valid Nonecovered by 2804:4a34::/32 636 100% 67
2804:4a34:6000::/48 Valid Nonecovered by 2804:4a34::/32 636 100% 67
2804:4a34:8000::/33 Valid Nonecovered by 2804:4a34::/32 636 100% 67
2804:4a34:8000::/34 Valid Nonecovered by 2804:4a34::/32 636 100% 67
2804:4a34:c000::/34 Valid Nonecovered by 2804:4a34::/32 636 100% 67
45.231.192.0/22 Valid Other IRR onlyRADB, TC 671 100% 67
45.231.192.0/23 Valid Other IRR onlyRADB 671 100% 67
45.231.194.0/23 Valid Other IRR onlyRADB 671 100% 67
45.231.192.0/24 Valid Other IRR onlyRADB 670 100% 67
2804:4a34::/32 Valid Other IRR onlyRADB, TC 636 100% 67

AS-SET

PeeringDB's irr_as_set for AS267224: AS-SET:AS267224 AS-ALL. 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 (AS267224 isn't in the set, or no route object for AS267224 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 objectsAS267224 in itNot covered
AS-SET:AS267224 In no IRR database read today.
AS-ALL RADB 5173 No 17
AFRINIC (also) 111 No 17
APNIC (also) 1133 No 17
ARIN (also)1 member set in no database: AS30164:AS-CUSTOMERS 3114 No 17
RIPE (also)1 member set in no database: AS-SDN-CLINIC-LAB 235301,989 No 17

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

  • Route object: none12
  • Route object: RIR5
  • AS-SET: not found1
  • AS-SET: own ASN1
ChangePrefix or setDetailFull-table peers
Route object: none45.231.193.0/24No route object for it. A route object for 45.231.192.0/23 with origin AS267224 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267224 in the RIR database for the space.670 of 673
Route object: none45.231.194.0/24No route object for it. A route object for 45.231.194.0/23 with origin AS267224 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267224 in the RIR database for the space.670 of 673
Route object: none45.231.195.0/24No route object for it. A route object for 45.231.194.0/23 with origin AS267224 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267224 in the RIR database for the space.668 of 673
Route object: none2804:4a34::/33No route object for it. A route object for 2804:4a34::/32 with origin AS267224 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267224 in the RIR database for the space.636 of 636
Route object: none2804:4a34::/34No route object for it. A route object for 2804:4a34::/32 with origin AS267224 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267224 in the RIR database for the space.636 of 636
Route object: none2804:4a34:1000::/48No route object for it. A route object for 2804:4a34::/32 with origin AS267224 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267224 in the RIR database for the space.636 of 636
Route object: none2804:4a34:1001::/48No route object for it. A route object for 2804:4a34::/32 with origin AS267224 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267224 in the RIR database for the space.636 of 636
Route object: none2804:4a34:4000::/34No route object for it. A route object for 2804:4a34::/32 with origin AS267224 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267224 in the RIR database for the space.636 of 636
Route object: none2804:4a34:6000::/48No route object for it. A route object for 2804:4a34::/32 with origin AS267224 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267224 in the RIR database for the space.636 of 636
Route object: none2804:4a34:8000::/33No route object for it. A route object for 2804:4a34::/32 with origin AS267224 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267224 in the RIR database for the space.636 of 636
Route object: none2804:4a34:8000::/34No route object for it. A route object for 2804:4a34::/32 with origin AS267224 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267224 in the RIR database for the space.636 of 636
Route object: none2804:4a34:c000::/34No route object for it. A route object for 2804:4a34::/32 with origin AS267224 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267224 in the RIR database for the space.636 of 636
Route object: RIR45.231.192.0/22Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR45.231.192.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR45.231.194.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR45.231.192.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR2804:4a34::/32Route object only in RADB, TC. Add it in the RIR database for the space.636 of 636
AS-SET: not foundAS-SET:AS267224PeeringDB names AS-SET:AS267224; no IRR database read has it.
AS-SET: own ASNAS-ALLAS267224 isn't in AS-ALL (RADB) once expanded. Add AS267224 to it.

Route objects not announced

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