bgpreport

Network · data from 2026-11-12

AS267614 SIGAON SERVICOS TELECOMUNICACOES EIRELE

Registry name: AS267614 - SIGAON SERVICOS TELECOMUNICACOES EIRELE, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS267614, 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.
2804:43fc:4000::/48 Valid Nonecovered by 2804:43fc:4000::/34 636 100% 67
45.71.108.0/22 Valid Other IRR onlyRADB 668 99% 67
2804:43fc::/32 Valid Other IRR onlyRADB 634 100% 67
2804:43fc::/34 Valid Other IRR onlyRADB 352 55% 65
2804:43fc:4000::/34 Valid Other IRR onlyRADB 352 55% 65
2804:43fc:8000::/34 Valid Other IRR onlyRADB 352 55% 65
2804:43fc:c000::/34 Valid Other IRR onlyRADB 352 55% 65
45.71.108.0/23 Valid Other IRR onlyRADB 208 31% 56
45.71.110.0/23 Valid Other IRR onlyRADB 208 31% 56
45.71.108.0/24 Valid Other IRR onlyRADB 21 3%low visibility 10
45.71.110.0/24 Valid Other IRR onlyRADB 21 3%low visibility 9
45.71.109.0/24 Valid Other IRR onlyRADB 20 3%low visibility 9
45.71.111.0/24 Valid Other IRR onlyRADB 20 3%low visibility 9

AS-SET

PeeringDB's irr_as_set for AS267614: AS267614: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 (AS267614 isn't in the set, or no route object for AS267614 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 objectsAS267614 in itNot covered
AS267614:AS-ALL RADB 1311,654 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 13 are in fix.csv.

  • Route object: none1
  • Route object: RIR12
ChangePrefix or setDetailFull-table peers
Route object: none2804:43fc:4000::/48No route object for it. A route object for 2804:43fc:4000::/34 with origin AS267614 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267614 in the RIR database for the space.636 of 636
Route object: RIR45.71.108.0/22Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR2804:43fc::/32Route object only in RADB. Add it in the RIR database for the space.634 of 636
Route object: RIR2804:43fc::/34Route object only in RADB. Add it in the RIR database for the space.352 of 636
Route object: RIR2804:43fc:4000::/34Route object only in RADB. Add it in the RIR database for the space.352 of 636
Route object: RIR2804:43fc:8000::/34Route object only in RADB. Add it in the RIR database for the space.352 of 636
Route object: RIR2804:43fc:c000::/34Route object only in RADB. Add it in the RIR database for the space.352 of 636
Route object: RIR45.71.108.0/23Route object only in RADB. Add it in the RIR database for the space.208 of 673
Route object: RIR45.71.110.0/23Route object only in RADB. Add it in the RIR database for the space.208 of 673
Route object: RIR45.71.108.0/24Route object only in RADB. Add it in the RIR database for the space.21 of 673
Route object: RIR45.71.110.0/24Route object only in RADB. Add it in the RIR database for the space.21 of 673
Route object: RIR45.71.109.0/24Route object only in RADB. Add it in the RIR database for the space.20 of 673
Route object: RIR45.71.111.0/24Route object only in RADB. Add it in the RIR database for the space.20 of 673

Route objects not announced

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